-
Guiding question
What are the metadata needs for realizing this analysis? -
Considerations XML-tags [article (beginning & end), title (beginning & end), image, issue number, issue date, page number], library standards, interoperability
-
Goal Metadata structural framework
-
Discussants Mary Elings (lead), Teresa Schultz & Elena Azadbakht
- Listen:
Session 2 audio recording PART 1
Session 2 audio recording PART 2
Session 2 audio recording PART 3 - View: Session presentation slide deck
- Read: Session notes
- Briefing Documents:
- Schreibman, Susan, Raymond George Siemens, and John Unsworth. 2018. A new companion to digital humanities. http://www.credoreference.com/book/wileydh
- Martin-Rodilla, Patricia, and Cesar Gonzalez-Perez. 2019. "Metainformation scenarios in Digital Humanities: Characterization and conceptual modelling strategies". Information Systems. 84: 29-48.
In this session, we discussed the essential though often understated role metadata play with respect to digital humanities projects, particularly the importance of building metadata schema suited to a particular disciplinary context. With the goals of the project in mind, we discussed several potential metadata standards and how well suited they might be to the disciplinary scope of a digital history project.
Additionally, this session addressed the different types of required metadata to describe the assets within the collection, spending time distinguishing what the smallest unit of the collection might be (whether a particular page, article, journal issue, or year) and how we might associate all related assets within a database structure.
Having concluded that the collection would be divided into units at the article level and collected by both issue and year, we resolved to:
- explore Function Requirements for Bibliographic Records (FRBR), an entity-relationship model created by the International Federation of Library Associations and Institutions. FRBR would be the most viable method for describing the resources within our collection, and it is more user friendly than XML-based standards like The Encoding Initiative (TEI).