Agreements (UXPROD-573)

[UXPROD-1517] Support export of entitlements in current agreements for discovery systems Created: 04/Feb/19  Updated: 16/Sep/20  Resolved: 26/Aug/19

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q3 2019
Parent: Agreements

Type: New Feature Priority: P3
Reporter: Owen Stephens Assignee: Owen Stephens
Resolution: Done Votes: 0
Labels: ERM, agreements, po-mvp, q2-2019-spillover, team-mvp
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by ERM-215 Export Agreement data as KBART Closed
is defined by ERM-265 Export Agreement data as JSON Closed
is defined by ERM-327 Export entitlements as JSON from sing... Closed
is defined by ERM-328 Export entitlements as KBART from sin... Closed
Relates
relates to ERM-385 Export of Agreement content as JSON d... Closed
relates to ERM-386 Export of Agreement content as JSON d... Closed
relates to ERM-387 Agreement content KBART export | corr... Closed
Epic Link: Agreements
Front End Estimate: Medium < 5 days
Front End Estimator: md331 (Inactive)
Back End Estimate: Medium < 5 days
Back End Estimator: steve.osguthorpe
Development Team: Bienenvolk
PO Rank: 86
PO Ranking Note: This is a go-live requirement for GBV and Leipzig "ERM Only" implementations. It is essential for these institutions to be able to show what e-resources are available in their user-facing discovery systems
Rank: Chalmers (Impl Aut 2019): R5
Rank: Chicago (MVP Sum 2020): R2
Rank: Cornell (Full Sum 2021): R4
Rank: Duke (Full Sum 2021): R5
Rank: 5Colleges (Full Jul 2021): R5
Rank: FLO (MVP Sum 2020): R4
Rank: GBV (MVP Sum 2020): R1
Rank: hbz (TBD): R1
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R4
Rank: Leipzig (Full TBD): R1
Rank: Leipzig (ERM Aut 2019): R1
Rank: TAMU (MVP Jan 2021): R4
Rank: U of AL (MVP Oct 2020): R5

 Description   

Create export of entitlements which are part of "current" agreements. "current" defined by
(Status = Active) AND (("Is Perpetual" == "Yes") OR (("agreement start date" =< today OR not-populated) && (today =< "agreement end date" OR not-populated))

This applies to local KB only.

Out of scope:

  • export of full (MARC-style) bibliographic descriptions


 Comments   
Comment by Theodor Tolstoy (One-Group.se) [ 08/Feb/19 ]

For Chalmers, it seems this would be possible to do within HLM.

Comment by Anya [ 25/Feb/19 ]

Via Khalilah Gambrell "This feature is not applicable to any customer using EBSCO KB."

Comment by md331 (Inactive) [ 22/Mar/19 ]

Front-end estimate assumes being able to use stripes-components' ExportCsv component but having to make a decent amount of changes to support our non-RMB backend.

Comment by Jag Goraya [ 04/Jul/19 ]

Owen Stephens based on the comments in ERM-265 Closed , sounds like we may need a few additional stories to present/configure a user interface to set/trigger export processing:

1. export (filtered-by-agreement set?) from specific agreement
2. export (full or custom-filtered set?) from general settings (would this be via local-kb-admin app rather rather than an individual agreement?)
3. configure automated export schedule

Both with presumably

  • an export format option (JSON/KBART),
  • file export destination,
  • perhaps some error display if needed (are these long processes)?

And, of course, some permissions to ensure the feature set is not patron-accessible.

Can you confirm please? We're currently aiming for Sprint 68 for this. Thx

Comment by Jag Goraya [ 16/Jul/19 ]

Updated description to confirm that this is local kb only, as per sprint 68 planning session (cc Owen Stephens)

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