Discovery and/or creation of Eresources (UXPROD-577)

[UXPROD-1643] KB Data integrity checking and error handling Created: 11/Apr/19  Updated: 16/Sep/20  Resolved: 16/Sep/19

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Q3 2019
Parent: Discovery and/or creation of Eresources

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

Issue links:
Defines
is defined by ERM-182 On sync with remote KB, keep TIPPs wh... Closed
is defined by ERM-183 Log issues with remote KB sync Closed
is defined by ERM-338 Log import/sync errors on package import Closed
Relates
relates to ERM-443 Remove "existing coverage statements ... Closed
relates to ERM-506 KB Local Admin | Export import logs a... Closed
relates to UXPROD-2111 Local KB Admin | Improvements up to Q... Closed
relates to ERM-335 Define spec for upload file Closed
relates to UXPROD-1791 Manage Local KB Admin Closed
Epic Link: Discovery and/or creation of Eresources
Development Team: Bienenvolk
PO Rank: 84
PO Ranking Note: This feature relates to UXPROD-1791 and UXPROD-1513. Once it is possible for users to import data from a wider variety of data sources, it is important to ensure that this does not lead to the import of data that is either definitely incorrect or is not allowed by the data model (e.g. 'e-resources must have titles')
Rank: Chalmers (Impl Aut 2019): R4
Rank: Chicago (MVP Sum 2020): R4
Rank: Cornell (Full Sum 2021): R5
Rank: Duke (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R3
Rank: FLO (MVP Sum 2020): R4
Rank: GBV (MVP Sum 2020): R2
Rank: hbz (TBD): R4
Rank: Hungary (MVP End 2020): R4
Rank: Lehigh (MVP Summer 2020): R4
Rank: TAMU (MVP Jan 2021): R4
Rank: U of AL (MVP Oct 2020): R4

 Description   

When importing a package list or syncing with an external KB, we will want to log when certain data problems are encountered so that a librarian/systems support can investigate and get the problem fixed in the remote KB.

Error logs will be presented in the Local KB Admin app ( ERM-290 Closed ).

Provisional UI mockups: https://drive.google.com/drive/folders/1qsNadX-m3k1NNDoM55prDfv_Kvy6u2Ws



 Comments   
Comment by steve.osguthorpe [ 04/Jun/19 ]

What should we do with the incompatible coverage statements? Throw them away? Attempt to combine them? My guess is we just throw them away?

Comment by Martina.Schildt [ 02/Jul/19 ]

Erroneous data may be imported, but as noted in the description error logging and forwarding the error message to those responsible is important.

Comment by Jag Goraya [ 16/Jul/19 ]

Updated description to broaden the scope of the feature to non-coverage error conditions.

Previously:

This feature is specifically to relax the constraints on coverage data to allow Agreements to accept general TIPP data while rejecting incompatible coverage data (coverage end date being before a coverage start date).

When relaxing this constraint we will also want to log/note somewhere that this problem was encountered so that a librarian/systems support can investigate and get the problem fixed in the remote KB.

Comment by Jag Goraya [ 17/Jul/19 ]

Linking this feature to ERM-335 Closed which could be useful for extending the error conditions to log. See also Slack.

Comment by Cate Boerema (Inactive) [ 23/Aug/19 ]

Owen Stephens can you please give this an epic? Thanks!

Comment by Jag Goraya [ 16/Sep/19 ]

Released in Daisy (3.2)

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