Topic / Who | Tickets | Notes | Decision |
---|
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1030 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1433 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-309 |
---|
|
| This ticket is requesting that the extent calculator also creates a further extent for digital objects linked to the record. I can see a practical use for this but wonder if it would duplicate extents created in resource records for digital material? Might be useful for users know that there are X number of digital objects linked to a resource record. Requesting alternative way to find required report on the reports page. Issue flags that the current layout is difficult for screen readers to navigate. Recommend for user testing or request a specification?
| |
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1260 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1417 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1423 |
---|
|
| Metadata Standards just issue a call for feedback on extents for the MARC importer, so I suggest moving this ticket to awaiting more information. Deaccession subrecord publishing is currently an all or nothing affair governed by a config setting. This ticket would like a publish checkbox added to the subrecord in order to selectively publish deaccession subrecords. I support this ticket, but I think the tooltip for the publish checkbox should note that it will only be published if the config option is also enabled. This ticket is asking for four additional features for the Collection Management subrecords: Implement the download CSV feature from the browse view. Since this capability is already present in most browse views, it seems like it would be straightforward to do. Enable the Collection Management subrecord on archival objects, as well as resources, accessions, and digital objects. I think this is a great idea, it makes the subrecord much more flexible. Ability to set a Collection Management subrecord as completed or inactive. This functionality already exists in more flexible manner than suggested by using the “Processing Status” field. Add a “Supplies Used” field. I don’t see any downside to adding this.
|
|
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1356 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1458 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1462 |
---|
|
| | |
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-1464 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-889 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-10 |
---|
|
| | |
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-31 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-334 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-358 |
---|
|
| | |
| Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-538 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-562 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-666 |
---|
|
| | |
|
| | |