...
The system should provide a link or a button that will allow a user to indicate they would like to create a new instance to
be attached to the bibliographic record they are currently looking at the instances off.
When user clicks the 'Create Instance' ‘Create Instance’ button, the result should be to display the instance editor with new (empty) instance and child item – should be represented on the left hand menu (with a placeholder) so the user has the ability to navigate to the details of the child item and back to the details of the instance. In addition, this will allow users to navigate to the other (existing) instances and items and to create multiple items on the new instance.
...
If the user attempts to click the "Create Instance" “Create Instance” button while they are working on an un-submitted new
instance, present an error message
1) If the user attempts to click the "Create Instance" “Create Instance” button while they are working on an un-submitted new instance, present an error message ("Cannot “Cannot create additional new instance. Unsaved instance exits."”).
2) If the user attempts to leave this page with an un-submitted new instance, warn them they will lose any unsaved data (An unsaved instance exists are you sure you want to exit? Yes/no) .
...
Each Instance should have an icon next to it that when clicked will create a new item within that instance
When user clicks the 'New ‘New Item Icon/Button' Button’ button, the result should be to display the item editor with new (empty) item – should be represented on the left hand menu (with a placeholder) so the user has the ability to navigate to the details of the item. In addition, this will allow users to navigate to the other (existing) items and to create multiple items on the new instance.
...
If the user attempts to click the "Create Instance" “Create Instance” button while they are working on an un-submitted new
instance, present an error message
1) If the user attempts to click the "Create Item" “Create Item” button while they are working on an un-submitted new item, present an error message ("Cannot “Cannot create additional new item. Unsaved item exits."”).
2) If the user attempts to leave this page with an un-submitted new item, warn them they will lose any unsaved data (An unsaved item exists are you sure you want to exit? Yes/no) .
...
Scenario | Question | Answer | |
When the instance is being displayed the instance.instanceIdentifier (System-assigned unique ID for the Instance Document.) should be visible. When an item is being displayed the item.itemIdentifier (Maps to MFHD 876 $a Internal item number - System-assigned unique ID) should be visible. | Where we need to display this Information? | Display at the top of each tab | |
Metadata fields (Last Updated by, Date) | Which data we need to display?( Means Holdings will contain its own data and item records will have its own data. Also, from docstore, we will get dateEntered and lastUpdated only. What about updated By, Created) | When click on holdings, display holding metadata and when click on Item display Item data. | |
For Audit, asking to show at least 10 update initially ( | From where we can get this information? | Need to implement logic in docstore (maintain Version) | |
ACCESS METHOD & RELATIONSHIP / REQUIRED FIELDS [5]: These fields are only required if electronicLocationAndAccess element is used. | Here what "used" “used” means? | Refers to Required field. Means if Electronic Location & Access tab is used, then [5] is mandatory | |
Referring to User requirements document, we do have mock UI screens for Holdings tab-Location, Serial and Action Notes. | What about remaining tabs? | No mock-ups | |
Holdings and Item tabs | Form where we can get data for dropdown fields? | Refer OLE-2806 | |
| What is the max-length for "token" “token” fields? |
|
|