OAI-PMH Support (UXPROD-993)

[UXPROD-2439] Form OAI-PMH response using filtering conditions in set Created: 27/May/20  Updated: 25/Jan/24

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: TBD
Parent: OAI-PMH Support

Type: New Feature Priority: P3
Reporter: Anastasiia Zakharova Assignee: Magda Zacharska
Resolution: Unresolved Votes: 0
Labels: consortia-ebsco, external_sys_int, firebird-po-share, loc, oaipmh
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by MODOAIPMH-151 Reflect sets list modifications in OA... Open
is defined by MODOAIPMH-152 Filter records list by set filtering ... Open
is defined by MODOAIPMH-153 Filter records list by set filtering ... Open
is defined by MODOAIPMH-154 Include set membership information in... Open
Relates
relates to UXPROD-2406 Implement sets CRUD for OAI-PMH - fro... Closed
relates to UXPROD-2841 Implement sets CRUD for OAI-PMH - bac... In Refinement
relates to MODOAIPMH-211 Perform validation for all sets and f... Open
relates to UIOAIPMH-17 Sort sets in OAI-PMH setting Open
relates to MODOAIPMH-212 Enrich /oai-pmh/sets endpoint with su... Open
relates to UIOAIPMH-19 Updated value of the set filtering co... Open
relates to UIOAIPMH-23 Highlight set with validation issues ... Open
relates to UIOAIPMH-13 Search OAI-PMH sets Draft
Epic Link: OAI-PMH Support
Front End Estimate: XL < 15 days
Front End Estimator: Magda Zacharska
Front-End Confidence factor: 20%
Back End Estimate: XXXL: 30-45 days
Back End Estimator: Magda Zacharska
Back-End Confidence factor: 20%
Development Team: Firebird
PO Rank: 5
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R4
Rank: GBV (MVP Sum 2020): R4
Rank: MO State (MVP June 2020): R2
Rank: U of AL (MVP Oct 2020): R2

 Description   

Currently, OAI-PMH allows selective harvesting only by date.
With sets implementation, it is going to provide an opportunity to define harvested collections based on more granular options.
OAI sets configuration will be available via GUI and it might require modification to the implemented functionality in UXPROD-2406 Closed feature to meet use cases as defined below.

Scope

  • Provide a way to build or reuse existing query to define collection to be harvested
  • Define permission set that will allow only authorized users to define sets

Out of scope
tbd

Use cases:

  • I would like to be able to combine a bunch of locations into a single set. We have an associated K-12 school with its own library as part of our structure. I would like to harvest just the K-12 library data. I would like to create a set that includes all of the K-12 locations and not a separate set for 200 locations.
  • Special collections libraries might want to contribute a set of their records to a union catalog. Perhaps that might be based on subject. It would definitely be done for all records of items that have digitizations (think DPLA or Europeana). Or even just to match the metadata records with their own digital assets management systems, for combined display in discovery systems, since DAMS often have much less robust descriptive metadata.
  • To harvest what libraries think of as a collection, so harvesting by campus or library are major use cases for consortia.
  • Being able to build sets from a list of material types is very useful. This is a bigger deal than it sounds because of the continued (and unfortunate) practice of libraries loading huge numbers of subscription electronic records in their catalogs that don't belong in such a harvest.

Additional information
More information on sets can be found by link http://www.openarchives.org/OAI/2.0/openarchivesprotocol.htm#Set.



 Comments   
Comment by Magda Zacharska [ 21/Dec/23 ]

Changing theĀ  release assignment as the implementation requires further discussion with LC.

Generated at Fri Feb 09 00:23:59 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.