OAI-PMH Support (UXPROD-993)

[UXPROD-2841] Implement sets CRUD for OAI-PMH - backend work Created: 07/Dec/20  Updated: 21/Dec/23

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

Type: New Feature Priority: P3
Reporter: Hkaplanian Assignee: Magda Zacharska
Resolution: Unresolved Votes: 0
Labels: external_sys_int, loc_dependency, oaipmh, split
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File Set modification.png     PNG File Sets setting page.png    
Issue links:
Cloners
clones UXPROD-2406 Implement sets CRUD for OAI-PMH - fro... Closed
Defines
is defined by MODOAIPMH-211 Perform validation for all sets and f... Open
is defined by UIOAIPMH-17 Sort sets in OAI-PMH setting Open
is defined by MODOAIPMH-212 Enrich /oai-pmh/sets endpoint with su... Open
is defined by UIOAIPMH-13 Search OAI-PMH sets Draft
Relates
relates to UIOAIPMH-19 Updated value of the set filtering co... Open
relates to UXPROD-2439 Form OAI-PMH response using filtering... Draft
Epic Link: OAI-PMH Support
Front End Estimate: Out of scope
Back End Estimate: XXXL: 30-45 days
Back End Estimator: Magda Zacharska
Back-End Confidence factor: 20%
Development Team: Firebird
PO Rank: 0
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   

This is a UXPROD-2406 Closed spillover from 2020 R3 with the backend work for implementing sets for OAI-PMH.

Currently, OAI-PMH allows selective harvesting only by date.
With sets implementation, it is going to provide an opportunity to harvest by different fields, e.g. location, record type, discovery suppression etc.

Sets configuration should be flexible enough and available via user interface, so that librarians can form their own sets structure. Separate page “Sets” in Settings->OAI-PMH is to be created. Here sets can be searched, viewed, created, duplicated, modified and deleted, according to the user’s permissions (see designs attached).

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

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.

Questions:

  1. Is selecting one location going to resolve the problem?
  2. Can multiple sets be used during one harvest?
  3. Which of the following is the correct approach for saving setSpecs:
  • <setSpec>test</setSpec>
  • <setSpec>mycustomentry</setSpec><setSpec>audio-role-only</setSpec>
  • <setSpec>mycustomentry:audio-role-only</setSpec>


 Comments   
Comment by Oleksii Petrenko [ 01/Mar/23 ]

Hello Magda Zacharska. Is it possible to keep single fix version for feature? I removed Q-release. I guess that separate feature for Q-release would be great. Sorry for inconvenience. Thank you

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:27:17 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.