...
| JIRA | | serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | UXPROD-3342 |
|---|
|
Problem(s):
- Users will update inventory record details and this does not updated order details
...
Requirement | Status | Use cases |
|---|
When enumeration, chronology or copy number are edited in item record the linked piece is updated
| | Users may need to edit input errors in the enumeration, chronology, copy number fields after the item has been received |
| Data import may need to update enumeration, chronology, copy number fields after the item has been created |
| Catalogers editing item details after the point of receipt would always be thinking of inventory. Could be two different sets of enumeration and this needs to be changed to a different one. These users may not have received permissions |
| Smaller operations may have a single user that has all permissions but after point of receipt this user would also focus on the inventory interface when correcting or updating these fields. |
| For standing orders and periodicals in particular it is important to keep this data in these records in sync. Eg. if the item enumeration is changed to 3-4 but the piece is still 3, a user looking at receiving history may mistakenly think that issue 4 was never received. |
| Receiving data is not necessarily describing "what was ordered" so much as what was received. This is in many ways dependent on how information is captured and how it evolves in inventory as the representations of this material become more specific. For this reason it also makes sense that the data be kept in sync. |
User is able to change the instance connection of POL and move all related items
See | Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | UXPROD-3619 |
|---|
|
| | Serials title change can be major and require a new instance be created. This is rarely caught at point of receipt meaning that once the new instance is created the library would move one or more items to the new record |
| One scenario we encounter often is a firm ordered monograph gets ordered on its own bib record but later it needs to get moved to a different mono continuation record--so this would involve moving the item to another holding on a different Instance record. Generally this would mean getting rid of the bib after as it is no longer needed. |
| Often times materials that need to be moved would already be received. However it is possible that we discover the material while it is On order and want to correct it immediately |
| I would say it is very common for us to do. maybe a few in one month, more than 5-10 some months We have a project right now with more than 100,000 items that need to be collapsed into a single holdings on the instance. Well, it happen every day for me, and when it does it's very time consuming, but it's way less than the number of things I process "normally" |
Proposed workflow:
https://miro.com/app/board/uXjVPPrQbuE=/?share_link_id=870031371969
Questions:
Question | Status | Conclusion | Comments |
|---|
| |
|
|
...
Work Breakdown Structure:
| Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | issuekey in linkedIssues("UXPROD-3342") AND issueLinkType = defines |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
|