Enable management of the reference data values in picklists in both Agreements and Licenses applications
(UXPROD-2259)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | Q3 2020 | Parent: | Enable management of the reference data values in picklists in both Agreements and Licenses applications |
| Type: | New Feature | Priority: | TBD |
| Reporter: | Owen Stephens | Assignee: | Owen Stephens |
| Resolution: | Done | Votes: | 0 |
| Labels: | erm, round_iv | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||||||
| Epic Link: | Enable management of the reference data values in picklists in both Agreements and Licenses applications | ||||||||||||||||||||||||||||
| Development Team: | Bienenvolk | ||||||||||||||||||||||||||||
| Rank: Chicago (MVP Sum 2020): | R4 | ||||||||||||||||||||||||||||
| Rank: Cornell (Full Sum 2021): | R4 | ||||||||||||||||||||||||||||
| Rank: Duke (Full Sum 2021): | R1 | ||||||||||||||||||||||||||||
| Rank: 5Colleges (Full Jul 2021): | R2 | ||||||||||||||||||||||||||||
| Rank: 5Colleges (ERM Jun 2020): | R4 | ||||||||||||||||||||||||||||
| Rank: GBV (MVP Sum 2020): | R2 | ||||||||||||||||||||||||||||
| Rank: hbz (TBD): | R4 | ||||||||||||||||||||||||||||
| Rank: MO State (MVP June 2020): | R4 | ||||||||||||||||||||||||||||
| Rank: TAMU (MVP Jan 2021): | R4 | ||||||||||||||||||||||||||||
| Rank: U of AL (MVP Oct 2020): | R4 | ||||||||||||||||||||||||||||
| Description |
|
Currently Agreements accepts whatever resource types (serial, monograph, journal, book, audiobook, ...) are supplied by external sources. This creates challenges for knowing how to treat these types in terms of search and display (in the latter case especially in terms of the "coverage" display which can be a date range for serial resources and a year/edition/volume for monograph resources) To help control these offer a user configurable list of types and how they should be handled as 'monograph' or 'serial' in terms of search and display Additionally integrations with eHoldings or other external knowledgebases need to be considered as these external KBs will have their own list of "types" |