Download presentation
Presentation is loading. Please wait.
Published byThomas Anderson Modified over 6 years ago
1
Fedora at UT Libraries Melanie Cofield, Metadata Coordinator
Audrey Templeton, Software Developer/Analyst
2
{ Context Fedora & Islandora repos DSpace IR
Home grown PHP/MySQL sites Tape and server storage Drupal dark archive GLIFOS Archive-It Campus Digital Asset Management Task Force { Human Rights Documentation Initiative
3
Infrastructure AWS Fedora 3 Islandora 7.3-1.5 Staffing:
3 software developers, 3 system admins, 1 UX, 2 Web developers 1 metadata coordinator Project/content owners At the present time we are using Amazon Web Services for a majority of our instances and are running Fedora 3, topped by Islandora Our staffing at present is 3 software developers, 3 system administrators, 1 content designer, 2 web developers, 1 metadata coordinator, and the Project/Content owners, who in most cases are very hands on in this process.
4
Content Streaming video Art, architecture, and design images
Language research recordings, images, and texts Archival documentation from Latin American partners Communications assets (images and video) Our content in production right now consists of · Streaming Video · Art, Architecture and Design images · Language research recordings, images, and text · Archival documentation from our Latin American partners. Still in testing and development are Communications Assets (images and video from various campus partners), a workflow tool for our digitization unit, and several other projects.
5
Streaming video Licensed, purchased, owned videos, digitized for streaming + UTVideoMD (a metadata schema created by a former staff member), assets ingested to Fedora; ingest process sends copy to Wowza & generates streaming URL that is added to catalog record for access.
6
Visual Resources Collection Accessioning Tool
Art, architecture, and design images VRC is a back end workflow tool for the Fine Arts Visual Resources Collection created using an Islandora interface on top of Fedora 3. Images are requested by Professors and the VRC staff create the digital object, gather the metadata, and publish the TIFF and metadata to a public facing tool called DASE (Digital Archive SErvices database managed by Liberal Arts ITS) using forms, custom modules and drush to create the fedora objects and a nightly cron to push changes to DASE. This project was a long one for the development team, and we gave the client a few nice upgrades from their previous accessioning tool including a feature where changes to their authority lists cascade throughout the repository making manual updates unnecessary.
7
Archive of the Indigenous Languages of Latin America
Language research a/v recordings, images, and texts Disciplinary repository for data management requirements Contract migration from homegrown archive to Islandora MODS MADS custom schema Persons - 4,392 Organizations - 34 Countries - 28 Languages - 391 Collections - 150 Resources - 14,518 Media Files - 108,636 Goals: pilot for contracting out for Islandora development; improved interface for search/browse, self-deposit options, streamlined workflows for archive staff Contract with Truman Technologies/dgi: March 2015-June 2016 Project team: archive manager, metadata coordinator, software developer Anticipated launch: mid-late Fall 2016 Linked Data: URIs of authority objects stored in affiliated Collections, Resources, and Media objects’ metadata
8
Latin American Digital Initiatives
Archival documentation on human rights, race, ethnicity, and social exclusion Post-custodial archival collaboration with Latin American partners In-house development of Islandora repository Partners’ DC MODS Books, Periodicals, Newspapers Pamphlets, Posters Documents, Clippings Collections - 4 12,274 images Goals: pilot for in-house Islandora development Grant period: May 2014-November 2015 Project team: project archivist, metadata coordinator, software developer, web designer, web developer, GRA Launched November 2015, redesign released May 2016 Batch ingest only at this point - forms in development Linked Data: URIs for place and country names, format and genre terms, repository names, and languages in MODS authority & value attributes: Place of Publication MODS: <originInfo><place><placeTerm> Authority: ISO 3166 Examples of authority and value attributes: authorityURI=" valueURI=" Format MODS: <genre> Authority: Library of Congress Thesaurus for Graphic Materials authorityURI=" valueURI=" Repository MODS: <location><physicalLocation> Authority: Virtual International Authority File (VIAF) authorityURI=" valueURI=" Subject - genre MODS: <subject><genre> Authority: Faceted Application of Subject Terminology (FAST) headings authorityURI=" valueURI=" Subject - geographic MODS:<subject><hierarchicalGeographic> <country>/ <region>, <city> authorityURI=" valueURI=" Language MODS:<language><languageTerm> Authority: ISO639-2b Examples of authority attribute: authorityURI="
9
Support services Consultations 20 AWS instances 2 local instances
16 sandboxes 4 production sites 2 local instances Islandora Interest Group Consultations: Developers meet with clients, assess needs, request islandora site, do initial setup, consult and assist in creating forms, views, script ingests, etc. The metadata coordinator meets with clients to assess needs and help with metadata mapping, form building, access and sharing strategies. Instances: sandboxes (Architecture Library, School of Architecture, College of Fine Arts, TIS, digitization, center for teaching and learning, BCAH and more); production sites (VRC, LADI, AILLA, islandora-tx [BCAH site]); Local instances: Digitization Services & Communications Islandora Interest Group: formed late 2014, as forum and group learning avenue for campus stakeholders. Members include staff from UTL, Briscoe Center for American History and School of Architecture, among others, and it is open to the campus community. Monthly meetings at various locations around campus, list-serv, wiki.
10
Looking ahead Synthesizing lessons learned from project-based strategies DAMS for UT Libraries Migration path from legacy systems to Fedora Migration path for Fedora 3 to 4 Preparing for Linked Data
11
Questions?
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.