150 likes | 165 Vues
This project aims to implement a Digital Asset Management System (DAMS) at NLW, with the goals of ingesting, managing, and disseminating digital objects. The system will support digitization, digital archiving, and digital collection projects while ensuring open access within a rights-managed environment. The implementation will be managed by a dedicated group, and various software tools such as FEDORA and VITAL will be utilized.
E N D
DAMS Implementation at NLW20th February 2007 Paul Bevan paul.bevan@llgc.org.uk
A DAMS for NLW • Marketplace Review • Consultancy Review – FEDORA & DSpace • Pilot Project • What can we achieve? • What work is to be done? • Procurement as part of Integrated Library Management System. • Virtua, Vital, Verify, etc
DAMS Implementation • Key Goals: • Ingest, manage and disseminate objects • Support current and future digitisation, digital archiving and digital collection projects • Achieve seamless integration • Provide a platform for future dissemination methods • Open access to our digital data, within a rights-managed environment • Secure our assets in a way which is open to preservation
Managing the Implementation • Staffing: • Implementation Group comprising mix of standards, IMS project management, technical, and digitisation staff. [Carried over from pilot] • 2 DAMS Implementation Managers (Systems & Technical) • Key interactions with other personnel as required. • Communication: • Implementation Group Meetings • Project Board Reports • dev Wiki
About FEDORA • Flexible Extensible Digital Object and Repository Architecture • Strong userbase • Open-Source • Clear development pattern • Flexible! • Extensible!
About VITAL • Product of VTLS Inc. • Based on FEDORA • Client • Access Portal • VALET • Handle Server • Allows the flexibility of Open Source within a managed and supported framework. • Certain Developments Required • Shift to Fedora 2.1 (complete) • Integration (Authentication) • Live Failover (DataGuard) • Our Platform • Vital 3 • Fedora 2.1.1 • Oracle 10i • Twin Servers (with live failover)
Approach • Object Review (complete) • Prioritisation(Digitised Still Images) (complete) • Defining Object Types (complete) • Make existing Digital Archive accessible (complete) • METS (complete) • Develop Ingest Processes • Develop Management Processes (eg. Checksumming) • Testing and Final Ingest • Release 1: Transparent Dissemination of Digitised Still Images (March 2007)
Access Points & Metadata (Overview) • Access Via • PRIMARY: Catalogue (Single Sign On…) • SECONDARY: ‘Exhibitions’ • TERTIARY: OAI-PMH, PIs • Metadata • METS & MARC : Administrative & Descriptive • Split to minimise inconsistencies (but, NLSing…) • METS holds policy, therefore outside of FEDORA (but enforced by FEDORA) – future proofing. • METS as SIP, AIP and DIP
VITAL Disseminators OAIS METS MARC MARC Virtua METS METS Digital Archive METS
Example: Rights-Access • METS = Policy, FEDORA = Enforcement • FEDORA uses XACML (eXtensible Access Control Markup Language) to enforce rights on one or a group of objects within the repository. Rights are based on XACML statements constructed from the METS:Rights from METS document. • Example Policies: Repository-wide Policy • Deny access to the deleteDatastream method of API-M if user is not “author” Object-specific Policy • Deny all access to the object “llgc:100” if user is a not located within Wales. Genre-oriented Policy • Given that an object conforms to the content model type of “journal-article,” deny access to the “getFullArticle” if the user is not in the group “registered” Time-oriented Policy • Permit users access to “embargoed” datastream of digital archival collection after January 06, 2009
All Objects must Contain METS DS DC DS (OAI-PMH) Relationships DS Objects below collection level must contain Object Files (!) DS: METS DS: DC (OAI-PMH) DS: Relationships Near-Line Tape Store DS: Object (eg. TIFF File) Referenced Referenced Fast Image Server DS: Object (eg. JPEG File) DS: Object (eg. Thumbnail File) …. Referenced Content Model: Object (AIP) Example Object (Digitised Still Image)
Content Model: Book Book-Level Object llgc:001 DS1: METS DS2: DC DS3: Rels-Ext Is part of Is part of Is part of Page-Level Object llgc:002 DS1: METS DS2: DC DS3: Rels-Ext DS4: Archive Image DS5: Reference Image DS6: Thumbnail Image Page-Level Object llgc:003 DS1: METS DS2: DC DS3: Rels-Ext DS4: Archive Image DS5: Reference Image DS6: Thumbnail Image Page-Level Object llgc:004 DS1: METS DS2: DC DS3: Rels-Ext DS4: Archive Image DS5: Reference Image DS6: Thumbnail Image Relationships can exist one-way but are identifiable from both levels
Content Model: Collection (Admin) Collection-Level Object: Jpeg File DataStreams llgc:100 DS1: METS DS2: DC DS3: Rels-Ext Is part of Is part of Is part of Is part of Book-Level Object llgc:011 DS1: METS DS2: DC DS3: Rels-Ext Book-Level Object llgc:001 DS1: METS DS2: DC DS3: Rels-Ext Is part of Is part of Page-Level Object llgc:014 DS1: METS DS2: DC DS3: Rels-Ext DS4: Archive Image DS5: Reference Image DS6: Thumbnail Image Page-Level Object llgc:002 DS1: METS DS2: DC DS3: Rels-Ext DS4: Archive Image DS5: Reference Image DS6: Thumbnail Image Note: Levels are arbitrary
Next Steps • Further Object Types: • Other Digital Still Images(CNC) • Audio-Visual Resources • ePrints • Digital Archives • Self-Deposit • Websites • More Varied Disseminations: • Project/‘Exhibition’ websites • Interactivity • Preservation Tasks