UI | Add Instance Source URI for Description to Inventory Instance Administrative Data
CSP Request Details
None
CSP Rejection Details
None
CSP Approved
None
Description
The purpose of this feature is to create a new field for a URI in the Inventory Instance administrative metadata accordion. This field will be populated when an instance record is created from an external source of non-MARC data. The only valid value would be a single URI and the field is not repeatable. Since the value is generated as part of the record creation process and the data is managed externally, it should not be editable in the Inventory UI or via Bulk Edit. Since it will not be used for MARC data, it also need not be accounted for in the current iteration of Data Import.
This URI would provide a bridge between a description maintained in a shared cataloging environment such as Sinopia, Share-VDE, Libris (National Library of Sweden), or Blue Core, and FOLIO Inventory.
Use case(s)
As a metadata practitioner I want to be able to connect easily to an external authoritative source of a linked data description.
I want to be able to go directly to the external source from the instance record, if the external source needs updating.
I want to be able to use this external source to generate, update, and potentially instance data [not necessarily via data import]
Scenarios
Scenario
Login to FOLIO environment, as user with the necessary permissions to view and edit Inventory instances
Navigate to Inventory and select an instance record that has been generated from an external linked data store (e.g., instance source = Sinopia) [need get a screen shot from Stanford?]. Instance source is not FOLIO or MARC
When viewing the administrative metadata accordion in the instance detail view, I see a new field with label “Instance Source URI.” The field immediately follow the Source element. The field contains an actionable (hyperlinked) URI. The full URI may or may not display completely, as long as the hyperlink functions.
The contents of this field must be a single URI. The field is not repeatable.
Scenario
When viewing the same record in Edit mode, the field is populated but is frozen (cannot be edited), and the box is grayed out. [mock-up here – make sure it does not appear actionable] The behavior should be similar to how the electronic access URL is implemented.
Scenario
In edit mode, the Instance Source URI box is responsive (can be expanded to view longer text)
Out of scope: behavior of rest of instance data in edit mode; searching by the value in this element
URIs may be needed in additional Inventory Instance values such as related BIBFRAME Works, subjects, and contributors, but are considered out of scope for this request. The development work required to enable opening an Instance for editing in a shared cataloging environment external to FOLIO referenced above is out of scope for this issue. This field will be populated when an instance record is created from an external source (as noted above). Employing a single value constraint, the only valid value would be a single URI and the field is not repeatable. Since the value is generated as part of the record creation process and the data is managed externally, it should not be editable in the Inventory UI or via Bulk Edit. Since it will not be used for MARC data, it also need not be accounted for in the current iteration of Data Import.
The purpose of this feature is to create a new field for a URI in the Inventory Instance administrative metadata accordion. This field will be populated when an instance record is created from an external source of non-MARC data. The only valid value would be a single URI and the field is not repeatable. Since the value is generated as part of the record creation process and the data is managed externally, it should not be editable in the Inventory UI or via Bulk Edit. Since it will not be used for MARC data, it also need not be accounted for in the current iteration of Data Import.
This URI would provide a bridge between a description maintained in a shared cataloging environment such as Sinopia, Share-VDE, Libris (National Library of Sweden), or Blue Core, and FOLIO Inventory.
Use case(s)
As a metadata practitioner I want to be able to connect easily to an external authoritative source of a linked data description.
I want to be able to go directly to the external source from the instance record, if the external source needs updating.
I want to be able to use this external source to generate, update, and potentially instance data [not necessarily via data import]
Scenarios
Scenario
Login to FOLIO environment, as user with the necessary permissions to view and edit Inventory instances
Navigate to Inventory and select an instance record that has been generated from an external linked data store (e.g., instance source = Sinopia) [need get a screen shot from Stanford?]. Instance source is not FOLIO or MARC
When viewing the administrative metadata accordion in the instance detail view, I see a new field with label “Instance Source URI.” The field immediately follow the Source element. The field contains an actionable (hyperlinked) URI. The full URI may or may not display completely, as long as the hyperlink functions.
The contents of this field must be a single URI. The field is not repeatable.
Scenario
When viewing the same record in Edit mode, the field is populated but is frozen (cannot be edited), and the box is grayed out. [mock-up here – make sure it does not appear actionable] The behavior should be similar to how the electronic access URL is implemented.
Scenario
In edit mode, the Instance Source URI box is responsive (can be expanded to view longer text)
Out of scope: behavior of rest of instance data in edit mode; searching by the value in this element
URIs may be needed in additional Inventory Instance values such as related BIBFRAME Works, subjects, and contributors, but are considered out of scope for this request. The development work required to enable opening an Instance for editing in a shared cataloging environment external to FOLIO referenced above is out of scope for this issue.
This field will be populated when an instance record is created from an external source (as noted above). Employing a single value constraint, the only valid value would be a single URI and the field is not repeatable. Since the value is generated as part of the record creation process and the data is managed externally, it should not be editable in the Inventory UI or via Bulk Edit. Since it will not be used for MARC data, it also need not be accounted for in the current iteration of Data Import.