LC Tenants Structure Development - ECS (UXPROD-4561)

[UXPROD-4569] LC Tenants Structure support > Data export (Firebird) Created: 20/Nov/23  Updated: 08/Feb/24

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: Ramsons (R2 2024)
Parent: LC Tenants Structure Development - ECS

Type: New Feature Priority: P2
Reporter: Khalilah Gambrell Assignee: Magda Zacharska
Resolution: Unresolved Votes: 0
Labels: LC-priority2, ecs, firebird-ecs-placeholder, loc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
clones UXPROD-4568 LC Tenants Structure support > Bulk-e... Draft
Relates
relates to UXPROD-4561 LC Tenants Structure Development - ECS Open
relates to UXPROD-4476 Support exporting local holdings and ... Closed
relates to UXPROD-4477 Export SRS records enriched with inve... Closed
relates to UXPROD-4570 Merge duplicate instances (ECS and no... Draft
Epic Link: LC Tenants Structure Development - ECS
Front End Estimate: Medium < 5 days
Front End Estimator: Vadym Shchekotilin
Front-End Confidence factor: 70%
Back End Estimate: XXXL: 30-45 days
Back End Estimator: Viachaslau Khandramai (Inactive)
Back-End Confidence factor: 30%
Development Team: Firebird
PO Rank: 0

 Description   

Work needed to support LC Tenant Structure support > data export and OAI-PMH workflows 

In scope for data - export:

  1. For the central tenant:
    1. Support default export job profile for instances and authority records (deleted and undeleted records)
    2. Support default export job profile for holdings that will allow exporting holdings stored in the data tenants
    3. Support custom mapping profiles that will allow exporting shared instances enriched with local holdings and items stored in data tenants
    4.  Exporting the entire collection that includes all instances enriched with holdings and items from all members
    5. Support exports based on lists of records UUIDs across all tenants
    6. Supports exports based on CQL statements generated on the central tenant level
  2. For a member tenant: 
    1. Support default export job profile for local and shared instances
    2. Support default export job profile authority records (deleted and undeleted records) - to be confirmed
    3. Support default export job profile for holdings that will allow exporting holdings stored in the tenant
    4. Support custom mapping profiles that will allow exporting shared and local instances enriched with local holdings and items
    5. Exporting the entire tenant collection that includes all instances enriched with local holdings and items
    6. Support exports based on lists of records UUIDs across all tenants
    7. Supports exports based on CQL statements generated on the central tenant level

In scope for OAI-PMH:

TBD

 

Questions

OAI-PMH:

1. What are the use cases for harvesting a specific part of the collection ?

 

 

Use cases:

  1. ECS: In consortia environments there will often be users that support multiple member libraries. To increase efficiency they will require the ability to trigger exports without the need to switch active affiliation.
  2. ECS:  Exporting records to provide them to OCLC for Holdings management.


 Comments   
Comment by Magda Zacharska [ 08/Feb/24 ]

Removing OAI-PMH after the consultation with LoC.

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