- A platform where professors will be able to create classroom groups and sites for students to collaborate on class projects.
- A platform where all users will be able to self-create campus interest groups to collaborate on similar research interests across departments and titles, leading to great interdisciplinary research.
- A platform with a searchable directory of research happening at Northeastern, where if a research interest is searched, a list of people, groups, and articles would be yielded.
The Music Online database has long provided access to streaming recordings, scores, and scholarly information from the Jazz Library, Smithsonian Global Sound, Garland Encyclopedia of World Music, and Classical Scores collections. New content has recently been added to this repertoire. You may search each database separately or across the entire Music Online platform.
American Music is a history database that has songs by and about Native Americans, miners, immigrants, slaves, children, pioneers, and cowboys. Included are the songs of the Civil Rights movement, political campaigns, Prohibition, the Revolutionary War, the Civil War, anti-war protests, and more.
Classical Music Library includes more than 76,000 albums from the Medieval period through current times. This database is an excellent complement to the library’s Naxos and Database of Recorded American Music collections.
Classical Scores Library now contains Volumes 2-4, in addition to Volume 1. These scores provide a reliable and authoritative source for scores of the classical canon, as well as a resource for the discovery of lesser-known contemporary works. It includes full, study, piano, and vocal scores.
Contemporary World Music delivers the sounds of all regions from every continent. The database contains important genres such as reggae, worldbeat, neo-traditional world fusion, Balkanic jazz, African film, Bollywood, Arab swing and jazz, and other genres such as traditional music like Indian classical, fado, flamenco, klezmer, zydeco, gospel, gagaku, and more.
Popular Music Library contains a wide range of popular music from around the world, including hundreds of thousands of tracks from major genres in pop music, including alternative, country, electronic, hip-hop, metal, punk, new age, R&B, reggae, rock, soundtracks, and many more.
For more information about other library streaming media collections, check out the Streaming Media guide.
This workshop, presented on Wednesday, September 23rd, was the second workshop in a series focused on recording high-quality audio in your own home. Besides providing the basic information about the hardware and software required for recording audio, the motivation behind this workshop was to provide an effective framework for building one’s toolkit of audio recording equipment, with financial responsibility in mind.
Those who record their projects at home are most likely doing so out of necessity rather than choice. This is because recording in an untreated home is always less preferable to recording in a professional studio, even if for no other reason than concerns for acoustic quality. This also means that finances are very likely a concern when choosing what resources to buy/use for recording an audio project. The first thing one should consider when deciding which pieces of audio equipment (hardware or software) to invest in is the needs of the artist creating the project (or your own needs, if you are the artist). This will help determine which parts of a recording setup are most important to you, and therefore which pieces to invest the most money into.
For example, if you plan to do a lot of recording with vocals or acoustic instruments, it would be most wise to spend less (or no) money on things like a premium DAW (digital audio workstation) or third-party plugins. These software elements of a recording setup have no effect on the inherent quality of the audio that is being recorded. This would allow you to invest more of your budget into a high quality microphone and preamp combo, to ensure the captured audio is as clean as it can be. However, if you make most of your music using samples, electronic instruments, or recorded sounds to be edited, then the previously suggested scenario doesn’t make much sense for you. Instead, you would likely be much happier with a simple and inexpensive USB microphone, which eliminates the need for a preamp. This would allow you to instead invest into a premium DAW like Ableton, along with some third-party samplers, sample packs, MIDI peripherals, or other virtual add-ons to expand your electronic music toolkit.
Hopefully, this workshop as given those who are recording at home a more clear picture of which pieces of equipment are most important for their needs. This should help achieve high quality and also minimal cost for recording audio, regardless of the format or intended outcome.
Check here for info on future workshops:
Have you ever found yourself on an academic site that you think you should be able to use but are unable to see the material? Accessing Northeastern’s licensed resources while off-campus can be complicated for students, faculty, and staff. Especially right now, when so many researchers are studying or working from home, sites that you may have had automatic access to while on campus may not be as readily available.
Using links from Scholar OneSearch or the Databases A-Z list is the best way to ensure seamless off-campus access, but sometimes you may find your way to an academic article through another avenue and may not be sure if Northeastern users have licensed access or not. The LibKey Nomad browser extension can help to bridge these gaps and either establish access to third-party platforms or provide alternate options for the content.
To use LibKey Nomad, visit thirdiron.com/downloadnomad and choose your browser. Upon installation, you’ll be prompted to choose Northeastern University from a drop-down list of organizations:
After this one-time selection, if Nomad can establish access when browsing a site that hosts academic articles or e-books, Nomad will display a “Download PDF” button in the bottom left-hand corner of the page which will link directly to a PDF of the material:
If Nomad can’t establish access, it will instead show an “Access Options” button which will link you to the citation in Scholar OneSearch to check for other potential modes of access or offer a link to request the item through interlibrary loan:
Please note that not all resources will work with Nomad, particularly single magazine websites such as the Economist, Foreign Policy, or the Wall Street Journal. Check the Databases A-Z list for a proxied link if you believe Northeastern has access to a resource or ask the library for assistance. LibKey Nomad is currently compatible with Chrome, Firefox, Edge, Brave, and Vivaldi browsers.
Digital projects involve complex collaborative networks, and they are at their strongest when they draw on the many different kinds of expertise that their participants have to share. At the same time, it can be challenging to draw together all of those different contributions of information, requirements, needs, and ideas in a single place. How do we bridge the differences in technical, cultural, and disciplinary knowledge within these teams, and create shared documentation that can evolve effectively during the project’s full life cycle?
In the past few months, the Digital Scholarship Group has been experimenting with adapting the functional specification—a writing genre that originated in software application and system development—to serve as a tool for project communication. As part of the Northeastern University Library’s recent LibCon event (a departmental sharing of projects and ideas among colleagues), members of the DSG presented a panel session that explored various aspects of this work from different perspectives. This post draws on those presentations to give an overview of the features, challenges, and possibilities of functional specifications in a digital humanities applied research group.
The genre of the “functional specification” in its original context covers several different types of terrain. As Senior DSG Developer Rob Chavez and Associate Director for Systems Patrick Murray-John described it, it captures important contextual information about the purpose and objectives of the project, the features and functions of the tool being developed (from the perspective of specific users and their needs), and the actors and entities (e.g. users, roles, and data) that are involved.
There are numerous benefits from gathering this level of detailed information at the inception of a project. At the level of practical planning, it provides concrete information that in turn makes it easier to develop design specifications, technical specifications, development plans, and tests to determine when a project has been successfully completed: if the functional specification describes a search function that returns results ranked by relevance, we know we’re not done until that is working. Perhaps equally important for the DSG, the process of creating a functional specification fosters participatory collaboration among the project’s constituents and prompts deep thinking about what the project is really seeking to accomplish, and helps the project agree on what it really needs before putting effort into building a working version. It also pulls together information that may be helpful for other purposes (such as grant-writing or publicity).
The functional specification also sits within a wider network of tools. Patrick Murray-John showed how the written document provides detail on specific features (such as searching, or viewing a map, or uploading a new file) which then gets translated into specific programming or design tasks which are stored in project management tools such as an issue tracker. While the functional specification provides a road map, the issue tracker provides a view of progress being made and enables the daily coordination of tasks and effort that are so necessary within a collaborative team. When a given feature is prototyped and eventually completed, the functional specification can then be used again as a confirmation that the real needs of the project have been met, and it can also serve as a place to record unfinished work that may have been out of scope—which in turn might feed into a future phase of the project’s development, or support future fund-raising efforts.
Functional specifications, in their original context in the software development industry, typically operate within a fairly uniform technical team with a lot of shared skills and knowledge. As a result, the common practices and familiar features of this genre mostly focus on its practical and technical aspects: a data inventory, user stories, use cases, preconditions, the logical flow of operations from step to step within a given functional context. For the DSG, experimentation with functional specifications has focused on building out the genre in a few different directions. First, as DSG Director Julia Flanders described through the example of the Digital Archive of American Indian Languages Preservation and Perseverance (DAILP) project, the functional specification can function more effectively as a bridge between different parts of the project team if it includes deeper contextual information: not only user stories, but also detailed information about the motivations and investments of specific user communities, which in turn help the team understand how the project’s data is shaped and why. In the case of the DAILP, understanding the differing needs of language learners, academic researchers, and language experts within the Cherokee tribes is crucial to technical design and decision-making at every level. As the DSG develops templates and guidance for project teams in writing functional specifications, we are putting greater emphasis on those topics and urging projects to use the functional specification as a prompt for early conversation. The DSG has also been experimenting with involving project teams more fully with creating the functional specification itself, rather than treating it as a purely technical genre. DSG Associate Director Amanda Rust discussed her work with the project team for the Civil Rights and Restorative Justice Project (CRRJ) to develop detailed accounts of the project’s working processes and research, a process that has empowered the group to imagine the functional possibilities more concretely, and intensified their sense of involvement and investment in the development process.
As Senior Digital Library Developer David Cliff pointed out in his contribution to the panel, one of the important roles of the functional specification is to bring clarity and consensus about project scope, and to avoid miscommunication or the dreaded “scope creep” that can occur when functional requirements aren’t clearly laid out at the outset. At the same time, as he and others noted, research projects like these are by their nature prone to change as they explore new possibilities. And similarly the DSG, as an applied research group, is always venturing into unfamiliar territory where precise time estimates are difficult.
The functional specification must therefore tread carefully between attempting to pin things down too closely or prematurely, on the one hand, and leaving things so underspecified that a project is never done, on the other. Iteration plays an important role here: sometimes a project team needs to see a prototype of a search results display before they can imagine the full set of facets and options that will make it truly useful. To be most useful, the functional specification needs to be able to establish achievable interim goals while also keeping track of the project’s largest vision. It is thus always a living and evolving document, and as one audience member pointed out in the panel discussion, it needs to make that evolution possible.
The Digital Scholarship Group has thus far developed three draft functional specifications and a draft template which also documents our emerging practices in this area. In the coming year, there are several areas where further research and experimentation will be needed. First, we want to create a fuller template and more detailed documentation of how and when different parts of the functional specification are most useful, situationally. Second, we want to continue to experiment with involving project teams in the authoring process. Third, we need to develop effective means for translating specific functions from the specification into concrete development tasks (to be tracked via GitHub). And finally, we need to tackle the question of versioning, and create transparent mechanisms for allowing the specification to evolve without losing its documentary value or creating confusion.