Search Constraints
Filtering by:
Creator
Allinson, Julie
Remove constraint Creator: Allinson, Julie
Keyword
Metadata
Remove constraint Keyword: Metadata
1 - 2 of 2
Number of results to display per page
Search Results
-
- Description:
- Using Hydra to manage and present cultural heritage resources raises a set of interesting challenges that are beyond the scope of the traditional institutional repository. These include more complex data models, elaborate and varied workflows, richer descriptive metadata, support for more and varied controlled vocabularies, the requirement to manage larger objects comprised of larger files and multiple derivatives, support for IIIF, and a desire for richer viewing environments in general. In this presentation we will discuss these challenges and highlight examples and implementations that have gone ‘beyond the repository’. An audio recording of the session is available for download below. and A presentation at Hydra Connect 2016 described thus
- Keyword:
- International Image Interoperability Framework (IIIF), Connect 2016, Workflow, Hydra, and Metadata
- Subject:
- Hydra Project
- Creator:
- Allinson, Julie and Stroop, Jon
- Contributor:
- Princeton University Library and University of York
- Owner:
- rob@scientist.com
- Language:
- English
- Date Modified:
- 07/24/2023
- Date Created:
- 10/05/2016
- Rights Statement Tesim:
- In Copyright
- License Tesim:
- Creative Commons BY Attribution 4.0 International
- Resource Type:
- Presentation
-
- Description:
- As most Hyrax adopters know, Hyrax offers a basic set of metadata properties that it assigns to each new work type. Most adopters will extend that set, to a greater or lesser degree, adding new properties, defining vocabularies and terms lists, and setting other constraints and requirements. Adding new metadata is a complicated process in Hyrax, and there are various ways in which developers have worked to streamline things (eg. scooby snacks, dog biscuits and archetypes). But before we even get to customising a Hyrax application, metadata librarians and developers must collaborate on specifying the metadata requirements. With no community machine-readable approach to defining those requirements, misunderstandings are common, and can be costly. With a machine-readable specification for metadata, metadata librarians could accurately specify requirements and developers could validate and codify those into applications. That’s where the Machine-readable Metadata Modeling Specification (M3) steps in. The specification is the output of the M3 Working Group and is nearing its version 1.0 release. This presentation will provide a walkthrough of the specification, show how to construct and validate a new M3 profile, and illustrate the benefits of M3 for both metadata specialists and developers. and A presentation at Samvera Connect 2019 described thus
- Keyword:
- Hyrax, Metadata, Samvera, and Connect 2019
- Subject:
- Samvera Community
- Creator:
- Hutt, Arwen and Allinson, Julie
- Contributor:
- University of California San Diego and Notch8
- Owner:
- rob@scientist.com
- Language:
- English
- Date Modified:
- 07/24/2023
- Date Created:
- 10/24/2019
- Rights Statement Tesim:
- In Copyright
- License Tesim:
- Creative Commons BY Attribution 4.0 International
- Resource Type:
- Presentation