New Instance properties, 2018Q3
Description
Environment
Potential Workaround
Attachments
blocks
Checklist
hideTestRail: Results
Activity

Charlotte Whitt September 24, 2018 at 1:24 PMEdited

Wayne Schneider September 14, 2018 at 1:15 AM
New reference data have been added to the CI builds, they should appear in the next build.

Charlotte Whitt September 7, 2018 at 11:00 AM
Review by: :

Charlotte Whitt September 6, 2018 at 12:06 PMEdited
Hi - could you send me the table in a spread-sheet - then I can put in my answers in a column labeled PO's feedback. Thanks!

Niels Erik Nielsen September 6, 2018 at 10:55 AM
Type | Comments | |
---|---|---|
HRID | text field | Mandatory (breaking) |
- | - | Batch loader must populate with system control number for now |
- | - | Can only be done if Wayne has time to change the batch loader |
- | - | When creating Instance in ui-inventory, should user set it manually for now, or should it be set to the UIID if user does not enter anything? |
Instance status | text field, select | Will hold a UUID that references a Instance status term/code |
- | - | Does the ‘Instance status source’ describe who/what defined the term/code or who/what set the latest status on the Instance? |
- | - | Reference table is to be done later |
- | - | When the reference table is introduced, that will be a breaking change. |
Date status updated | text field | Marked mandatory (breaking) but assume it’s only if ‘Instance status’ is set? |
Catalogued date | text field | - |
Previously held | boolean | Default “no”? |
Staff suppress | boolean | Default “no”? |
Statistical code | array, selects | Reference table is to be done later, when table introduced it will be breaking change |
Suppress from discovery | boolean | Default “no”? |
Mode of issuance | text field, select | Reference table is to be done later, when table introduced it will be breaking change |
Cataloguing level | text field, select | Reference table is to be done later, when table introduced it will be breaking change |
Type | Comments | |
---|---|---|
<no new elements> | - | - |
Type | Comments | |
---|---|---|
<no new elements> | - | - |
Type | Comments | |
---|---|---|
Publisher role | array (strings) | - |
Format category | - | to be designed |
Publication date | (exists) | to be changed from date to yyyy, could be client-side-only change |
Publication frequency | array (strings) | - |
Publication range | array (strings) | - |
Type | Comments | |
---|---|---|
Electronic access | array (objects) | Object elements: link text (text), materials specified (text), URI (text), URL public note (text), URL relationship (text) |
Type | Comments | |
---|---|---|
<no new elements> | - | - |
Type | Comments | |
---|---|---|
<no new elements>? | - | “Other related titles”? Listed at this point in the spreadsheet but no Jira story assigned |
Type | Comments | |
---|---|---|
<no new elements> | - | - |
Type | Comments | |
---|---|---|
Index title | text field | - |
Succeeding title | - | Is this a relation to another existing Instance? Or a title written into this instance as text? The former would be required to link to the succeeding title for example |
- see 's comment about the CI build