Heorhii's Work

ARCH	Priority	Planned Completion date	Notes	Questions
Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration. Updating Authority mapping rules issues when upgrading from one release to another causing duplications with same UUID search issues	P1	ASAP	I think this requires a MG HF and it is needed for Nolana too. Lotus > MG upgrade — is probably okay to use below workaround. MG > Nolana upgrade – we need a plan at minimum Nolana > Orchid upgrade – we need to implement a fix Next steps Workaround > DI > Update Action profile OR delete and re-load Need to discuss with FSE hosting about mapping rules Meet with Sobha, Heorhii, Vijay, Pavlo, Slava, and Kyle Banerjee (IC) > I can schedule this meeting Long term: Investigate approach > a mechanism to update records when mapping rules are updated > update existing JIRA issue. Assign the existing JIRA with Heorhii Namchuk Natalia will schedule a meeting with Heorhii, Pavlo and Vijay
Unable to locate Jira server for this macro. It may be due to Application Link configuration.	P4		Next steps KG writes requirements
Unable to locate Jira server for this macro. It may be due to Application Link configuration.	P8		Next step Radhakrishnan Gopalakrishnan will review tests and determine if we need to continue work in Poppy or QAL. Remains low priority (next week)
Unable to locate Jira server for this macro. It may be due to Application Link configuration.	P2		Report 1: Global Headings Update report (for Orchid) Unable to locate Jira server for this macro. It may be due to Application Link configuration. Unable to locate Jira server for this macro. It may be due to Application Link configuration. Report 2: Failed updated: Linked bibliographic fields report (for Orchid/Poppy - depends on estimate) Unable to locate Jira server for this macro. It may be due to Application Link configuration. Unable to locate Jira server for this macro. It may be due to Application Link configuration. Report 3: Blind headings report (for Poppy) Unable to locate Jira server for this macro. It may be due to Application Link configuration. Unable to locate Jira server for this macro. It may be due to Application Link configuration. Unable to locate Jira server for this macro. It may be due to Application Link configuration. Unable to locate Jira server for this macro. It may be due to Application Link configuration.	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
Unable to locate Jira server for this macro. It may be due to Application Link configuration.	P3		Next steps KG writes requirements	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?)
Unable to locate Jira server for this macro. It may be due to Application Link configuration.	P5		Next steps KG writes requirements
Unable to locate Jira server for this macro. It may be due to Application Link configuration.	P6		Next steps KG writes requirements
Unable to locate Jira server for this macro. It may be due to Application Link configuration.	P7		Next steps Heorhii Namchuk reviews feature and documents questions