Instance Record. Accordion Electronic access. Implement new elements and reorder data - part 2
CSP Request Details
None
CSP Rejection Details
None
CSP Approved
None
Description
Environment
None
Potential Workaround
None
Attachments
7
- 26 Oct 2018, 12:11 PM
- 26 Oct 2018, 12:11 PM
- 27 Sep 2018, 12:45 PM
- 27 Sep 2018, 11:49 AM
- 13 Sep 2018, 11:54 AM
- 13 Sep 2018, 11:54 AM
- 13 Sep 2018, 11:54 AM
blocks
clones
is blocked by
relates to
Checklist
hideTestRail: Results
Activity
Show:
Charlotte Whitt October 26, 2018 at 12:14 PMEdited
Manually tested in FOLIO Snapshot http://folio-snapshot.aws.indexdata.com/, version @folio/inventory 1.4.1000302, using Chrome.
All changes verified in FOLIO Snapshot. All looks good.
Mike Taylor September 27, 2018 at 12:45 PM
Charlotte Whitt September 27, 2018 at 12:42 PM
Mike Taylor September 27, 2018 at 12:40 PM
Nope. I was not on the watcher list. But when I left a comment, it automatically added me, as it ought – to ensure that I would see any replies. But I definitely was not on the list before, yet I got the notification.
I will now re-remove myself, and see if I get notified about the reply you're about to leave.
Charlotte Whitt September 27, 2018 at 12:17 PMEdited
Hi @Mike Taylor - you were on the Watcher list. But now I have deleted you, and Tymek
Done
Details
Details
Assignee
Niels Erik Nielsen
Niels Erik NielsenReporter
Charlotte Whitt
Charlotte WhittTester Assignee
Charlotte Whitt
Charlotte WhittPriority
Development Team
Prokopovych
Fix versions
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created September 13, 2018 at 11:54 AM
Updated January 20, 2019 at 10:48 PM
Resolved October 26, 2018 at 12:15 PM
TestRail: Cases
TestRail: Runs
Q4 2018:
The Electronic access (group of fields) elements all implemented (UIIN-229) for the Q3 release. Q3, was very rough display - here for Q4 we'll implement the refined look, as shown in the UX-wireframe.
The relationship element was implemented as a simple element (string) but has to be a select list - see UX wireframe. (MODINVSTOR-190, UIIN-316)
Options provided by Laura Wright (9/12/2018)
The possible values are:
No information provided
Resource
Version of resource
Related resource
No display constant generated
- - - - - - - - -
Purpose: To re-order and extend the metadata in Inventory Instance record, the accordion Electronic access collected in accordance with the Metadata Management SIG discussions and the GAPS analysis done by the Data Migration Subgroup, which are captured in
Inventory Beta - Metadata Elements (tab: Instance Metadata for Inventory) https://docs.google.com/spreadsheets/d/1RCZyXUA5rK47wZqfFPbiRM0xnw8WnMCcmlttT7B3VlI/edit?ts=5b715226#gid=952741439 - see: column: B (UIIN-229), and column I (Electronic access)
Acceptance Criteria:
Inventory Beta - Metadata Elements, column I (Electronic access)
Fields where Jira Story UIIN-229, column B are in scope for this story
Elements with a check mark in column C is implemented for alpha, or later updates
Create, view, edit and clone mode of the instance record all need to be updated
The UI display should look like the attached UX wireframes
Metadata elements labels should be as shown in column A "Instance Metadata Elements" column (please pay attention to the label case
Form edit controls (and values, where applicable) are specified in the "Input Type" column
Repeatable fields are indicated in column G "Repeatable"
Required fields are indicated in column H "Required" - include asterisks where noted (these denote that the field is required)
Please note, some of these have input controls that will ensure they are populated (when records are created via the UI). Others will require a validation message if left blank but that is out of scope for this story
All other columns in the Inventory Beta - Metadata Elements (tab: Instance Metadata for Inventory) spreadsheet can be ignored