Details
-
Story
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
-
Prokopovych
-
Medium < 5 days
Description
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
TestRail: Results
Attachments
Issue Links
- blocks
-
UIIN-301 Settings page. Inventory > Instances + Holdings + Item > URL relationship (Electronic access)
-
- Closed
-
- clones
-
UIIN-229 Instance Record. Accordion Electronic access. 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
-
- relates to
-
MODINVSTOR-190 Implement reference table and end-point: electronicAccess.relationship
-
- 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
-
-
UIIN-318 Status for additional fields as well as changes to, moving of and reformatting of fields.
-
- Closed
-
-
UXPROD-1106 Analyse and implement 'missing' elements in the Instance Record - part 2
-
- Closed
-
-
UXPROD-153 Provide links to users: Bibliographic records are supporting links (URLs) to digital objects (e.g. table of contents, full texts).
-
- Closed
-