the evolution of the uc san diego library dams
Post on 05-Dec-2014
429 Views
Preview:
DESCRIPTION
TRANSCRIPT
The Evolution of the
UC San Diego Library DAMSDigital Initiatives Symposium, University of San Diego
April 9th, 2014
Roger Smith, Cristela Garcia-Spitz, Matt CritchlowUniversity of California San Diego Library
A Brief History….
• Origins of the DAMS at UCSD• Dark archive• DAMS content focused on SC&A, preservation• Development of a public access system (PAS)• Growth and refinement of our digital object
viewer• Events management and preservation
Governance
Why a new DAMS?
• Need to better manage and display complex objects, data curation data sets
• Implement revised data model and facilitate search engine discovery
• Provide enhanced curatorial tools• Implement collection level records• Desire to develop features collaboratively• Provide functionality for user comments
DAMS3 > DAMS4 Implementation
Jul-2012 Oct-2012 Jan-2013 Apr-2013 Jul-2013 Oct-2013 Jan-2014 Apr-2014 Jul-2014
Data Modeling Group DAMS4 Implementation Group
DAMS4 Usability
Group
Digital Library Steering Committee & Products Group
Data Modeling Group
Digital Library Products Group
Data Modeling Group
DAMS4 Implementation Team
DAMS4 Usability Group
Data Modeling Group• Develop data model & OWL/RDF Ontology• Consisted of 5 members from
Technology Services & Metadata Services• Met 2x week from Jul-Oct 2012
DAMS4 Implementation Team
Digital Library Products Group
Data Modeling GroupDAMS4
Implementation Team
DAMS4 Usability Group
DAMS4 Implementation Team• Implement the recently designed data
model and Hydra• Consisted of 6 members from
Digital Library Development, Research Data Curation, Technology Services, & Metadata Services
• Met weekly from Nov 2012 – Feb 2014
DAMS4 Implementation Groups
Digital Library Products Group
Data Modeling Group DAMS4 Implementation Team
DAMS Events DAMS Collection Records
DAMS4 UI Functionality
Group
DAMS4 Usability Group
DAMS4 UI Functionality Group• Assessed user interface (UI)
navigation & functionality• Consisted of 7 members from
Digital Library Development, Special Collections & Archives, Communications & Outreach, Metadata Services, Research Data Curation, Digital User Services
• Met 3 times from Aug-Dec 2013 & carried out 2 rounds of review
DAMS4 Usability Group
DAMS4 Usability Group• Conduct user testing• Consists of 3 members from
Digital Library Development, Research Data Curation, & Digital User Services
• Methodology TBD
Digital Library Products Group
Data Modeling Group DAMS4 Implementation Team
DAMS4 Usability Group
Digital Library Products Group
Digital Library Products Group• Oversees DAMS development• Consists of 8 members from
Digital Library Development, Research Data Curation, Technology Services & Metadata Services
• Meets bi-weekly
Digital Library Products Group
Data Modeling Group DAMS4 Implementation Team
DAMS4 Usability Group
Digital Library Products Group
Data Model
Collection
Object
Component
Relationship
Name
Role
Data Model Use Case: Thing 1, Thing 2
Thing 1, Thing 2
Hydra
• Homegrown -> Community Model• Open Source• Blacklight• Testable• Hydra Camps• Consultants: http://curationexperts.com/
DAMS Architecture
Challenges & Opportunities
• Dependency Chain– Challenge: Not a completely homegrown product anymore– Opportunity: We can be part of the larger community making
improvements to this framework.
• Hydra Working Groups– RDF– Archives
• New Stakeholders: Research Community– Self Deposit– Large Files
• Fedora 4• Optimized Preservation Strategy
More Information
Check out Digital Collections Beta:• http://library.ucsd.edu/dc
Learn more:• http://libraries.ucsd.edu/about/digital-library/ • http://libraries.ucsd.edu/services/data-curation/
Contact Us:• dlp@ucsd.edu
top related