ARCH | Priority | Planned Completion date | Notes | Questions | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Updating Authority mapping rules issues when upgrading from one release to another
| P1 | ASAP | I think this requires a MG HF and it is needed for Nolana too.
Next steps
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| P4 | Next steps
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| P8 | Next step
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| P2 | Report 1: Global Headings Update report report (for Orchid)
Report 2: Blind headings : Failed updated: Linked bibliographic fields report (for Poppy) Report 3: Blind headings report (for Poppy)
| Authority control reporting for Orchid/Poppy releases 1. List of :Support reporting: requirements prioritization. 3. "These reports may be accessible from Inventory app or Authority app or Export Manager or Data export " - which UI component is supposed to be used for this representation and which format it should have? (sketches are welcome to get clear picture of FE - BE way of interaction) 4. "These reports may be available as a csv export " - is this option available after outline of report on View or beforehand? - asking as it is possible to handle request on both FE or Back-end side. - is this csv supposed to be consumed by any other component? 5. "In addition Inventory or Authority app may have additional facets/filters to allow a user To filter Authority records based on whether the record is linked to a bib field/record or not. To filter bib records based on linked status of a bib field/record " - needs UI wireframes and more details as this functionality can be implemented on Front-End (w/o server call) or Back-End side. E.g.: if filtering or facet search is required only within loaded on UI records - then solution could be done on Front-end side only | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| P3 | Next steps
| Authority control - autolink per quickMARC bib record | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| P5 | Next steps
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| P6 | Next steps
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| P7 | Next steps Heorhii Namchuk reviews feature and documents questions | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
...