Automated creation of analytic catalog records for born digital journal articles
Download as PPTX, PDF1 like1,148 views
The document discusses the automated creation of analytic catalog records for born-digital journal articles using a modular platform integrated with HathiTrust. It outlines the workflow for both manual and automatic record creation, ensuring compliance with bibliographic metadata specifications. Additionally, it highlights the importance of properly formatted metadata for article ingestion and retrieval within the HathiTrust catalog.
Automated creation of analytic catalog records for born digital journal articles
- 1. Automated creation of analytic catalog records for born-digital journal articles Kevin S. HAWKINS @KevinSHawkins
- 3. 3
- 4. 4
- 5. 5
- 6. 6
- 8. 8
- 9. 9
- 10. 10
- 11. Opportunities • HathiTrust – offers a better infrastructure for development than DLXS – is certified by Trustworthy Repositories Audit & Certification (TRAC) • There’s growing interest among institutions in building a shared infrastructure for publishing. 11
- 12. mPach: what are we creating? • modular platform • tightly coupled with the HathiTrust repository • for open-access journals • all you need to publish and preserve an OA journal • will integrate with Open Journal Systems (OJS) 12
- 13. 13
- 14. mPach Prepper (1 of 8)
- 15. mPach Prepper (2 of 8)
- 16. mPach Prepper (3 of 8)
- 17. mPach Prepper (4 of 8)
- 18. mPach Prepper (5 of 8)
- 19. mPach Prepper (6 of 8)
- 20. mPach Prepper (7 of 8)
- 21. mPach Prepper (8 of 8)
- 27. HathiTrust’s Bibliographic Metadata Specifications When a HathiTrust partner institution provides a digital object for inclusion in HathiTrust, it must provide a catalog record in MARCXML format using fields as defined in the Bibliographic Metadata Specifications, an extension of MARC 21 minimal-level requirements.
- 28. What is the repository unit (barcode equivalent) for born-digital journals? an individual article
- 29. But … There is also metadata that relates to the journal as a whole, such as: • title of the journal • name of the publisher • place of publication What to do with these?
- 30. mPach’s solution: creating two kinds of records conforming to HathiTrust’s Bibliographic Metadata Specifications Serial record for the journal Analytic record for each article Created manually Created automatically by mPach’s Prepper
- 31. Workflow for manual creation of serial records (1/2) When a new journal comes along that will use mPach: 1. Journal editor fills out a form that asks for: – journal title – any alternative titles or abbreviations – any previous titles – any ISSNs related to the journal – a short description of the scope of the journal
- 32. Workflow for manual creation of serial records (2/2) 2. A serials cataloger will check to see if the HathiTrust catalog already contains a record for the journal (or for any previous titles). They will be modified, a new record will be created, or both—linking to the journal’s homepage.
- 33. Full view v. 4 (2014) - (original from University of Michigan)
- 35. So can users only discover articles by way of the journal homepage? Nope! The analytic records for each article will also be in the HathiTrust catalog, so you can find articles directly (if, for example, you search the catalog for a known article title).
- 36. Automatic creation of article records (1/2) To review, the user (e.g., the journal editor) uses mPach’s Prepper to prepare an article for ingest into HathiTrust. A combination of paragraph styles in Microsoft Word and manually entered metadata in Prepper ensures that the bibliographic metadata is properly encoded in JATS XML.
- 37. Automatic creation of article records (2/2) So because we’ll have data that is correctly structured and actually correct, we will be able to map from JATS XML to the fields required to create an analytic MARCXML record for the article. Each analytic record will be created automatically at the time that an article is ingested. Our crosswalk, developed with significant assistance from Steven Holloway at ATLA, was donated to the JATS community on the JATS wiki.
- 38. But how good are these records? Do they follow AACR2 or RDA? Not in the following ways: • Records will not have titles of articles transcribed according to AACR2/RDA; instead, they will be in the record as displayed in the article. • Names will be handled as the mPach user spelled them and divided them into forenames and surnames. • We haven’t bothered with choosing a main entry: all access points are added entries.
- 39. For anyone interested, I have an annotated handout of a working document showing how the analytic and serial records will relate to each other and the other components of mPach.