Details
-
Story
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
-
Medium < 5 days
Description
Q4 2018 (part 2):
Property | In detail view | In edit form | Missing parts (Q4/part 2) | Other comments |
---|---|---|---|---|
HRID | Q3 | Q3 | Many instance records will not have this populated | |
Date status updated | Q3 | NA | Empty, to be system set Part 2 | |
Catalogued date | Q3 | Q3 | There's some issue with the date displaying one day earlier on opening the form part 2 | Actually the issue seems to be the same in ui-users: Create a user, set an expiration date to today, save, verify on details, go back to edit: it shows as the day before in the component. |
Statistical code | Part 2 | Part 2 | Reference data in order to populate, but: | Some design of this may be outstanding NOTE: Charlotte will write up new jira: |
Purpose: To re-order and extend the metadata in Inventory Instance record, the accordion Administrative 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-223), and column I (Administrative data)
Acceptance Criteria:
- Inventory Beta - Metadata Elements, column I (Administrative data)
- Fields where Jira Story
UIIN-223- see: 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
- NEW The element 'Series statement' is placed in Administrative data, but this is to be in the Title data accordion - see closing comment in
UIIN-166
TestRail: Results
Attachments
Issue Links
- blocks
-
UIIN-302 Settings page. Inventory > Instances, Holdings, Items > Statistical code types
-
- Closed
-
-
UIIN-385 Settings page. Inventory > Instances, Holdings, Items > Statistical codes and Statistical code names
-
- Closed
-
-
UIU-1814 Settings page. Users > Statistical code types
-
- Closed
-
-
UIU-1815 Settings page. Users>General> Statistical codes and Statistical code names
-
- Closed
-
- clones
-
UIIN-223 Instance Record. Accordion Administrative data. Implement new elements and reorder data - part 1
-
- Closed
-
- is blocked by
-
MODINV-71 New Instance properties, 2018Q3
-
- Closed
-
-
MODINVSTOR-152 New Instance properties, 2018Q3
-
- Closed
-
-
UIIN-297 Cataloged date displays as a day early on entering Instance form.
-
- Closed
-
-
UIIN-298 Implement statistical codes
-
- Closed
-
- relates to
-
MODINVSTOR-173 Make Instance property `hrid` required
-
- Closed
-
-
UIIN-318 Status for additional fields as well as changes to, moving of and reformatting of fields.
-
- Closed
-
-
UIIN-166 Add accordions to the detailed view of the Instance Record
-
- Closed
-
-
UIIN-273 Add accordions to the edit view of the Instance Record
-
- Closed
-
-
UXPROD-1106 Analyse and implement 'missing' elements in the Instance Record - part 2
-
- Closed
-