1. Developing a Dark Archive for OJS Journals Yu-Hung Lin, Metadata Librarian for Continuing Resources, Scholarship and Data Rutgers University 1 10/7/2015

2. Overview  Rutgers University Libraries (RUL)  RUL Open Access Journals and OJS Platform  Rutgers University Community Repository (RUcore) and its tools  Design Metadata Application Profile (MAP) for archiving electronic open journals  Workflows  Next steps 2 10/7/2015

3. Rutgers University Libraries 10/7/2015 3

4. RUL Open Access Journals & OJS  RUL manages the following e-journals  Pragmatic Case Studies in Psychotherapy  The Electronic Journal of Boundary Elements  Journal of Rutgers University Libraries  Journal of Jazz Studies  New Jersey History  Open Journals Systems (OJS) – An open-source software to make open access publishing available worldwide 10/7/2015 4

5. Dark Archive Definition “An archive that does not grant public access and only preserves the information it contains. This can refer to a digital archive or repository as well as brick & mortar archive.” (University of Michigan) “Dark Archive: An archive that is inaccessible to the public. It is typically used for the preservation of content that is accessible elsewhere.” (California Digital Library) “Dark archive: A long-term preservation and not a public use collection. The metadata not indexed and can access only via DOI or local system identifier.” (RUL) 10/7/2015 5

6. Rutgers University Community Repository (RUcore)  Mission – Maintain the significant intellectual property of Rutgers University and preserve Rutgers unique collections  Over 500 digital collections  Over 33,000 resources including ETDs, SOAR articles, research data, and other digital special collections  Built on two complimentary architectures—data model and Fedora repository architecture 10/7/2015 6

7. Data Model Concept A data model should be designed to meet the user’s information needs. Find – Can the user find the information object? Identify – Does the descriptive metadata provide sufficient information for the user to know what s/he has found? Select – Can the user select the correct resources based on the information provided from the search results Obtain – Can the user obtain the resource? 10/7/2015 7

8. RUcore Data Model 10/7/2015 8 A good data model should be Understandable by the information manager and the user Context independent A Representation of "living data” Support the management and preservation of data RUcore tracks lifecycle and ecology of the data https://rucore.libraries.rutgers.edu/about/data_model.php

9. Lifecycle of the Resource 10/7/2015 9

10. OAIS Model 10/7/2015 10 The OAIS Functional Model http://nssdc.gsfc.nasa.gov/nost/isoas/

11. Workflow Management System (WMS) Web-based graphical user interface for  Uploading digital objects (images, data sets, digital text, etc.)  Creating metadata to describe and manage those objects. Supports two roles:  Administrator -- selects vocabularies and designs metadata templates to speed up the metadata creation process  Team member -- uploads objects and creates metadata by using the metadata templates 10/7/2015 11

12. Reasons for archiving E-Journals in RUcore  Best practices (DOAJ requirements)  Economies of scale  Collaborate in regional and national preservation initiatives such as DPN archive and DataCite 10/7/2015 12

13. OJS Dark Archive Object Structure 10/7/2015 13 XML-1 datastream Technical metadata Archival MASTER (etc.) Archival MASTER (Article 1) Archival MASTER (Article 2) OJS Dark Archive Journal 1 Journal 2 Issue 1 Issue 2 Issue 3 … Etc. Metadata (+ MODS)

14. Design Metadata Application Profile Metadata Application Profile contains: Descriptive metadata  Meet the minimal metadata requirement for the collaborative institutions (such as DataCite and DPN) where the data might be shared  A durable link to the access copy via descriptive event and a link in the abstract  Document the date of the creation of digital preservation masters to perform an audit to detect any differences between the access copy file(s) and the archived file(s)  “version creation” of a resource is documented in a descriptive metadata event 10/7/2015 14

15. Design MAP (Continued) Technical metadata  Document OJS version information  May vary by collection  README file Rights metadata  Ownership of the resource 10/7/2015 15

16. Workflows  Develop a template in WMS  Use a combination of batch load and template to automate the ingest process  Export OJS metadata to a spreadsheet for batch load  Upload digital file(s) and create a zip directory in a workstation  Use Fedora management software (dlr/EDIT) to enhance searching for journal administrators  Test and restore the open access journals back to the OJS platform 10/7/2015 16

17. Example of an Archival Record 10/7/2015 17

18. 10/7/2015 18

19. Next Steps  Plan dark archives for other digital collections  Monitor the file size to ensure the sync of both access and dark archive resource 10/7/2015 19

20. 10/7/2015 20 Thank you!