Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device.
Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Authority control reporting for Orchid/Poppy releases 1. List of :Support reporting: requirements prioritization. 2. UI wireframes on how it's expected to look like to properly build solution around actual UX expectations. 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
Authority control - autolink per quickMARC bib record 1. Details on autolink and expected outcomes from solutions side. Is that about to find authority by provided identifiers during creation / updating? if yes: - will User be able to choose if they want to selected / deselect automatic linkage (when possible)? - in case if autolinkage failed and fields left unlinked should it be reported? How exactly (format)? - details on Data Import process expected changes with autolinking applying (2 phases? - 1 actual entities import; 2 - linkage?)
@Heorhii Namchukreviews feature and documents questions
non-technical Questions:
Currently there is a filtering (facet-like) functionality implemented for Effective location (item) field within Browse call numbers. Does it work sufficiently? How it's supposed to be changed by adding ability to browse by call number type? How this functionality supposed to correlate with existing one conceptually and from UI/UX perspective?
Is it possible to have multiple call number types for one item? How this going to be counted in facets (will it be counted multiple times for one item)?
What is the difference between Search by Effective call number (item), shelving order and Browse call number functionalities? Is it supposed to get Search by effective call number changed as well as Browsing afterwards?
How should look like (mock-ups / wireframes are welcome) browsing with ability of facet selection items by call number types? How current UI/UX will be changed?
Is itfixed amount of call number types aggregations or always computed depends on present items with corresponding call number types?
"The schema type will be determined by the value of the call number type" - does that mean dynamic computation of call number type all the time? Or is it possible to setup type during data import?
"If the call number is not provided the default search will be Other scheme" - is it possible to provide more details here?
Browsing by call number types had been developed before. The question is where the development stopped and what conceptual trade-offs were taken?
How is call number type currently ingested / computed during the DI?
Will it be possible to choose multiple facets / filters by call number type (e.g.: LC and Dewey Decimal) and continue browsing by selected criteria?
@Khalilah Gambrell and @Christine Schultz please look through the list of initial questions. Some could seem trivial but lets try to address ones to point the conceptual boundaries.