Instance Record. Accordion Descriptive data. Implement new elements and reorder data - part 2
CSP Request Details
CSP Rejection Details
CSP Approved
Description
Environment
Potential Workaround
Attachments
clones
is blocked by
relates to
Checklist
hideTestRail: Results
Activity
Charlotte Whitt October 26, 2018 at 11:58 AMEdited
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.
Niels Erik Nielsen September 26, 2018 at 11:37 AMEdited
Right, but that would require folio-testing at least to come up. And the edition change is not visible until the back-end is merged (issue marked as blocked by that).
Charlotte Whitt September 26, 2018 at 11:35 AM
Hi - sounds good. I'll assign it to my self as tester. I'll pick it up hopefully later this evening.
Niels Erik Nielsen September 26, 2018 at 11:32 AMEdited
I think we can close this. One change is done UI-wise (edition->editions, the corresponding back-end issues can be closed once the back-end branches are merged).
The last outstanding issue, format category, should be covered by and associated back-end issues.
Though, testing and snapshot are not currently building, but this is what the formatting looks like for example, including the new publisher role:
Charlotte Whitt September 17, 2018 at 9:43 AM
Hi
re.:
i.e. pick the first, concatenate multiple)
Sounds right - to pick the first. Thanks!
Details
Details
Assignee
Niels Erik NielsenReporter
Charlotte WhittTester Assignee
Charlotte WhittPriority
P2
Release: Q4, 2018:
Property
In detail view
In edit form
Missing parts (Q4/part 2)
Other comments
Publisher role
Q3
Q3
Publishers are currently formatted as a simple string but are going to be in a tabular display. This reformatting will be part 2
Formatting done
Format category
Part 2
Part 2
Reference table change, will be part 2
Block with Format fields (properties: category, term, code, source) to be set as repeatable
Part 2
Part 2
Reference table change, will be part 2
Publication date change from date to yyyy
Part 2
Part 2
Isn't it already yyyy ? (Yes, seems I've misunderstood, closing it, NE)
UIIN-317
Edition, to change from string to array of strings
Part 2
Part 2
Breaking change, will be part 2 (UIIN-299) Done. Back-end merge pending (MODINV-78, MODINVSTOR-171)
Purpose: To re-order and extend the metadata in Inventory Instance record, the accordion Descriptive data 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-227), and column I (Descriptive data)
Acceptance Criteria:
Inventory Beta - Metadata Elements, column I (Descriptive data)
Fields where Jira Story UIIN-227, 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