Details
-
Story
-
Status: Closed (View Workflow)
-
TBD
-
Resolution: Done
-
ERM Sprint 146, ERM Sprint 147, ERM Sprint 149
-
Bienenvolk
-
Nolana (R3 2022)
-
TBD
Description
Purpose:
Some e-resource packages are only available to a set of organisations/consortia/regions. Following ERM-2306 a list of these constraints can be stored for each package. This story is to add populate this information when harvesting data from GOKb.
Requirements
There are two ways in which the relevant information is available from the GOKb package harvest in depending on the content of the //package/global tag which is already used to populate the availabilityScope
IF the <global> / availabilityScope == "Local" then use the content of //package/curatoryGroups/group/name to add values to the availabilityConstraints
e.g.
<package> <global>Local</global> ... <curatoryGroups> <group> <name>ZBW</name> </group> </curatoryGroups> </package>
IF the <global> / availabilityScope == "Regional" OR "Consortium" then use the content of //package/globalNote
e.g.
<package> ... <global>Consortium</global> <globalNote>ZBW</global> </package>
On updating an existing package the behaviour should be to remove all existing constraints and replace with ones in new package metadata
TestRail: Results
Attachments
Issue Links
- defines
-
ERM-2236 mod-agreements release. Fix version: 5.4.0
-
- Closed
-
-
UXPROD-3754 GOKb Package metadata enhancements in Agreements local KB
-
- Closed
-
- is cloned by
-
ERM-2308 Display list of availabilityConstraints in package display
-
- Closed
-
- requires
-
ERM-2306 Add availabilityConstraints to packages
-
- Closed
-
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...