samvera-labs / hybox-ideas Goto Github PK

Hydra consists primarily of the following 7 mappings:

1. repository representation (RDF) to object properties (Ruby)
2. object properties (Ruby) to repository representation (RDF)
3. object properties (Ruby) to an index representation (Solr)
4. index representation (Solr) to an HTML show page
5. object properties (Ruby) to an HTML form
6. HTML form output to object properties (Ruby)
7. index search results (Solr) to an HTML page

It would be excellent if these could be dynamically configurable. #4 and #7 have already been done in Spotlight. I think it's feasible to make the remaining 5 dynamically configurable as well. I'd suggest starting with #3.

Submitter: Justin Coyne

Provide integration with individual user Zotero accounts, allowing publications and data to be dynamically exchanged.

For example: http://id.loc.gov/authorities/names/no2012012521

If hyrda in a box wanted to be accessed by thousands of users who own a raspberry pi. I would love to help brainstorm about how that could work. [email protected]

Submitter: Derek Davis

At Boston College we assign handles to our digital objects before they are created. This is because the handle's suffix re-uses a unique identifier from another system such as our archival management system.

We need to be able to include these pre-composed handles in our ingest packages rather than being tied to handles that hybox would assign as part of a sequence.

For example, we assign a component unique identifier to a resource, BC1986_032_ref101,
which is mapped to OBJID in a METS document, resulting in the following handle generated on ingest

http://hdl.handle.net/2345.2/BC1986_032_ref101

Currently we ingest our handles using PREMIS in METS and would need a standards based place to store handles for ingest to HyBox.

As a user depositing an item, I need the ability to apply a standard rights statement, such as a copyright statement

mentioned by Ben Goldman

We need to migrate the over 5007 complex objects in our current repository to HyBox. Our complex objects include anywhere from one to hundreds of constituent files, each with multiple manifestations (master, reference image, index, etc.) The physical formats are photographs, individual manuscripts, and archival files**. Our current repository exports METS that we hope can (1) be ingested into HyBox either “as is” or after a transformation to PCDM or some other schema and (2) delivered to the user without further work after the ingest. Our METS application profile is fairly generic and straightforward. A typical example of one of our objects is http://dcollections.bc.edu/webclient/DeliveryManager?pid=437063

We'd be delighted to work on transformations or other tasks to help move this forward.

**The term archival file as it is used here refers not to a physical folder, but rather to one of the four levels of the ISAD(G) descriptive framework that recognizes four levels: fonds, series, file, and item. ISAD(G) is an internationally agreed metadata structure standard which ensures consistency across archival finding aids to enhance resource discovery.

http://www.crossref.org/fundref/

institutional repositories (and their depositors, and their depositors' funders) benefit from it

The Lincoln Archives Digital Project, www.lincolnarchives.us is digitizing all of the federal records housed in the National Archives. When completed 30 million records in hundreds of recoed groups, millions of entries will be scanned, and transcribed. Each entry is organized differently, chronologically, alphabetically, case number, etc.
Besides customizing the look, will it be possible to have a feature to select the way I want the entry organized, which will automatically create the entry, with the pages, can I import a spreadsheet for a particular entry which will contain thousands of documents, and Hydra will create the pages automatically, etc.
Will it be possible to have a comments section for each document to encourage discussion around that document?
Karen

Submitter: Karen Needles

ArchivesSpace "digital object" components are rather basic. Would be great if archivist could use hydra to link the physical collection management done in Aspace to a digital repository, and vice-verse.

Test

Submitter: Test

From Chealsye at CWRU: I recently joined Case Western and am new to Hydra. We're very interested in a batch ingest function for our repository. I've seen previous posts from LSE working on a batch ingest, Duke discussing batch ingest needs, and a post from WGBH stating that DCE is working on a batch ingest function for them in 2013. What progress has been made on a batch ingest function?

A question from Twitter in response to our presentation at DLF: https://twitter.com/nataliembaur/status/659134053048713216

any talk about international applications? Making it multilingual?

With a specific suggestion to target Spanish and possibly Portuguese.

Submitter: alberto martinez

We need ingest routines that (1) allow for the creation of SIPs for complex objects outside of the repository environment and (2) that result in DIPs with no further intervention from library staff. To elaborate, the parent object would be created as part of the ingest process, and, with no further intervention on the staff side, the ingest process would take in all the constituent files as well as the descriptive, structural, technical, and preservation metadata. The ingest process would then create a DIP that understands the relationships among the files in order to and facilitate navigation in the access layer.

This is needed because (1) we use external tools to create our complex objects and (2) our objects contain many constituent files that are not separately described. It is not sustainable or cost effective for us to manually build digital objects in the repository environment.

A use case:
we currently ingest METS digital objects that are exported from the Archivists Toolkit/ArchivesSpace. If needed, we have the capacity us to transform the METS into a different format for ingest to Hybox. For a detailed description see the 201500305 news item on the BLC wiki: http://blcspecialcoll.pbworks.com/w/page/73429475/FrontPage

Form editors that support to enable staff editing/creation of metadata. Supporting a variety of schemas would be nice. We have a significant stake in support for MODS which we use for our collections and for our feed to Digital Commonwealth, our DPLA Hub.

http://www.loc.gov/standards/mods/

Make it a really cool thing

Submitter: Mark Matienzo

As a repository manager, I need to be able to make metadata updates in bulk to selected items or whole collections

I submitted an idea here: https://docs.google.com/forms/d/16BiWACwtD4AARGe6P0IaMQl5rOeWDLdi6g6-6V3YGto/viewform?fbzx=-86786976012364307

When it was complete, it said I could see it here: https://github.com/projecthydra-labs/hybox-ideas/issues, but I don't see it.

Create an interface that identifies constituent files, enabling users to either (1) cite a particular physical or logical component or (2) use the labels to navigate to a particular location within the object.

We currently use the label attribute on mets:structMap/mets:div to accomplish identification and navigation. This object is an example of one photo shoot including 23 similar images that need to be individually identifiable/citable by users.

Suggested by Donna McCrea, University of Montana:

At a minimum, comply with Section 508 [1] and WCAG 2.0 [2]

[1] https://www.section508.gov/content/learn/laws-and-policies
[2] http://www.w3.org/TR/WCAG20/

For institutions that run an institutional repository, there seems to be some interest to add support for integration with Symplectic's API.

Hydra depends on many services, but the site may have partial functionality if some of the services are missing/degraded. It would be nice to have a status page that showed if the application was set up correctly. This would include:

• Connection to Solr
• Connection to Fedora
• Connection to Redis
• Job queue depth and any failures
• Status of queue workers (how many are working?)
• FITS exists on configured path
• imagemagick exists on the configured path
• soffice exists on the configured path
• ffmpeg exists on the configured path
• It should warn if the minter state file is in the tmp directory.

Submitter: Justin Coyne

so that it is possible to link to a user's ORCID profile and possible use the ORCID identifier itself as an account ID

Imagine being able to move content from a HyBox instance to a LOCKSS network - by API or harvesting? That could be really cool!

Submitter: Submitted by Hannah Frost on behalf of Tom Cramer

As a user depositing an item, I need the ability to apply a Creative Commons license from a menu of license options

Hiya, I'm a librarian in the UK and have responsibility for both archival materials and copyright at a Uni here, although my background is in the States.

There is an exception to copyright which allows libraries to digitise content and provide it as long as it's on dedicated computers, aka device-dependent access. However churlish this copyright 'exception' might seem, it can at least provide SOME access to our archival material and start the ball rolling on the digitising/metadata work that needs to go into making these materials accessible.

My suggestion comes out of an awareness of the different attitudes taken towards digitising cultural artifacts based on concerns about possible infringement.

Thanks
Lisa

Submitter: Lisa Redlinski

• Can an object belong to more than one collection?
• Can a collection have sub-collections?
• Do collections confer access metadata to their members?
• Does a collection identifier get encoded as part of the object identifier?
• Can you move an object from one collection to another?
• Are the members of a collection ordered?
• What metadata does a collection have?