Instance Record. Accordion Electronic access. 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

Charlotte Whitt September 21, 2018 at 11:50 AM
Hi - I have updated following sample records with electronic access descriptions, and deprecated the former url-element:
biometrics-and-neuroscience.json
global-africa-v1.json
global-africa-v3.json
umzetzung-v1.json
umzetzung-v2.json
bridget-jones-baby.json

Niels Erik Nielsen September 13, 2018 at 3:56 PM
Property | In detail view | In edit form | Missing parts (Q4/part 2 if not done today) | Other comments |
---|---|---|---|---|
Electronic access (group of fields) | Q3, very rough display | Q3 | Turns out 'relationship' will be a select list (see comment above), that bit will be part 2. The display of electronic access in detail view to be refined (part 2) |
|

Charlotte Whitt September 13, 2018 at 11:52 AM
- sounds all good. Thanks

Niels Erik Nielsen September 13, 2018 at 9:03 AMEdited
, this is the Q3 and part 2 designations for this issue, may change during the day (add to detail page) if time permits:
Property | In detail view | In edit form | Missing parts (Q4/part 2 if not done today) | Other comments |
---|---|---|---|---|
Electronic access (group of fields) | Part 2 | Q3 | Turns out 'relationship' will be a select list (see comment above), that bit will be part 2 |
|

Niels Erik Nielsen September 12, 2018 at 10:01 PMEdited
Actually the relationship will be a select list. Options provided by Laura Wright just now:
It's based on the value of the 856 2nd indicator. The possible values are
- No information provided
0 - Resource
1 - Version of resource
2 - Related resource
8 - No display constant generated
In other words one more reference table - to be implemented as per spreadsheet (simple text field) for Q3, as select list later.
Details
Details
Assignee

Reporter

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