Instance Record. Accordion Administrative data. Implement new elements and reorder data - part 1
CSP Request Details
CSP Rejection Details
CSP Approved
Description
Environment
Potential Workaround
Attachments
is blocked by
is cloned by
relates to
Checklist
hideTestRail: Results
Activity
Niels Erik Nielsen September 13, 2018 at 3:25 PMEdited
Property | In detail view | In edit form | Missing parts (Q4/part 2 if not done today) | Other comments |
|---|---|---|---|---|
HRID | Q3 | Q3 | Many instance records will not have this populated | To be mandatory in back-end later (breaking) Part 2. Needs a sequencer Part 2. Is mandatory in UI. If user enters a non-unique HRID a back-end alert will pop up, should be presented user-friendly(Part 2) |
Instance status | Q3 | Q3 | Reference data in order to populate |
|
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 |
|
Previously held | NA | Q3 |
|
|
Staff suppress | NA | Q3 |
|
|
Suppress from discovery | NA | Q3 |
|
|
Mode of issuance | Q3 | Q3 | Reference data in order to populate |
|
Statistical code | Part 2 | Part 2 | Reference data in order to populate, but: | Some design of this may be outstanding |
Cataloging level | Q3 | Q3 | Reference data in order to populate |
|
Niels Erik Nielsen September 13, 2018 at 2:26 PMEdited
Property | In detail view | In edit form | Missing parts (Q4/part 2 if not done today) | Other comments |
|---|---|---|---|---|
HRID | Q3 | Q3 | Many instance records will not have this populated | To be mandatory in back-end later (breaking) Part 2. Needs a sequencer Part 2. Is mandatory in UI. If user enters a non-unique HRID a back-end alert will pop up, should be presented user-friendly(Part 2) |
Instance status | Q3 | Q3 | Reference data in order to populate |
|
Date status updated | Part 2 | Part 2 |
|
|
Catalogued date | Q3 (raw form) | Part 2 |
|
|
Previously held | NA | Q3 |
|
|
Staff suppress | NA | Q3 |
|
|
Suppress from discovery | NA | Q3 |
|
|
Mode of issuance | Q3 | Q3 | Reference data in order to populate |
|
Statistical code | Part 2 | Part 2 | Reference data in order to populate, but: | Some design of this may be outstanding |
Cataloging level | Q3 | Q3 | Reference data in order to populate |
|
Niels Erik Nielsen September 13, 2018 at 2:01 PM
Property | In detail view | In edit form | Missing parts (Q4/part 2 if not done today) | Other comments |
|---|---|---|---|---|
HRID | Q3 | Part 2 | Many instance records will not have this populated | To be made mandatory later (breaking) Part 2. Needs a sequencer Part 2 |
Instance status | Q3 | Q3 | Reference data in order to populate |
|
Date status updated | Part 2 | Part 2 |
|
|
Catalogued date | Q3 (raw form) | Part 2 |
|
|
Previously held | NA | Q3 |
|
|
Staff suppress | NA | Q3 |
|
|
Suppress from discovery | NA | Q3 |
|
|
Mode of issuance | Q3 | Q3 | Reference data in order to populate |
|
Statistical code | Part 2 | Part 2 | Reference data in order to populate, but: | Some design of this may be outstanding |
Cataloging level | Q3 | Q3 | Reference data in order to populate |
|
Niels Erik Nielsen September 13, 2018 at 10:35 AM
Property | In detail view | In edit form | Missing parts (Q4/part 2 if not done today) | Other comments |
|---|---|---|---|---|
HRID | Q3 | Part 2 | Many instance records will not have this populated | To be made mandatory later (breaking) Part 2. Needs a sequencer Part 2 |
Instance status | Q3 | Part 2 | Reference data in order to populate |
|
Date status updated | Part 2 | Part 2 |
|
|
Catalogued date | Q3 (raw form) | Part 2 |
|
|
Previously held | NA | Q3 |
|
|
Staff suppress | NA | Q3 |
|
|
Suppress from discovery | NA | Q3 |
|
|
Mode of issuance | Q3 | Part 2 | Reference data in order to populate |
|
Statistical code | Part 2 | Part 2 | Reference data in order to populate, but: | Some design of this may be outstanding |
Cataloging level | Q3 | Part 2 | Reference data in order to populate |
|
Niels Erik Nielsen September 13, 2018 at 8:42 AMEdited
Property | In detail view | In edit form | Missing parts (Q4/part 2 if not done today) | Other comments |
|---|---|---|---|---|
HRID | Q3 | Part 2 | Many instance records will not have this populated | To be made mandatory later (breaking) Part 2. Needs a sequencer Part 2 |
Instance status | Q3 | Part 2 | Reference data in order to populate |
|
Date status updated | Part 2 | Part 2 |
|
|
Catalogued date | Q3 (raw form) | Part 2 |
|
|
Previously held | NA | Part 2 |
|
|
Staff suppress | NA | Part 2 |
|
|
Suppress from discovery | NA | Part 2 |
|
|
Mode of issuance | Q3 | Part 2 | Reference data in order to populate |
|
Statistical code | Part 2 | Part 2 | Reference data in order to populate, but: | Some design of this may be outstanding |
Cataloging level | Q3 | Part 2 | Reference data in order to populate |
|
Details
Details
Assignee
Reporter
Priority
P3
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