Who | Item | Notes | Decision |
---|
| Announcements/Questions? | | |
Terra
| Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-302 |
---|
|
| Would be a helpful feature but not necessarily high prioritization.
| thoughts? pass? |
Terra | Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-666 |
---|
|
| | |
Terra | Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-335 |
---|
|
| | |
Maggie | Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-760 |
---|
|
| Duplicated bug in test instance: http://test.archivesspace.org/staff/top_containers/10287 | |
Maggie | Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-300 |
---|
|
[Revisiting from last time - there was some confusion about it (Notes: Patrick Galligan (Unlicensed)suggest that this is a bug and not shouldn’t be a feature request | Ack, my agents weren’t published last time! Uploaded new screenshot on ticket. Rec: Pass. Think it does make more sense for Agents-as-Subjects to appear in Related Names section, as described in ticket. PUI: http://test.archivesspace.org/repositories/2/resources/345 | |
Maggie | Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-525 |
---|
|
| | |
Julia | Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-424 |
---|
|
| | |
Julia | Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-791 |
---|
|
| | |
Julia | Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-743 |
---|
|
| | |
Bill | Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-667 |
---|
|
| | |
Bill | Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-700 |
---|
|
| | |
Bill | Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-535 |
---|
|
| | |
Lora/Laney | Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-422 |
---|
|
| | |
Laney/Lora | Jira Legacy |
---|
server | System JIRA |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-493 |
---|
|
| | |
Lydia | Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-345 |
---|
|
| [It seems like the ASpace sandbox is slow today] Can replicate. Why is selecting an extent type only allowable? Perhaps this should be updated so that the two of them are required together and update the tooltip to say so? Also, if there is an error in saving, the error message is off the visible screen. It would be helpful if any error message (or at least something indicating that there is an error) is displayed within the screen view. Rec: Pass | |
Lydia | Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-514 |
---|
|
| Seeking community feedback about whether this is a good move. Obviously importing dummy dates isn’t good, but neither is not having good documentation on collections. Thoughts? | |
Lydia | Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-560 |
---|
|
| Seeking feedback, especially from Laney McGlohon (Unlicensed) Lora Woodford about mapping since this is shoehorning it from a different field. “Undated” would be nice to avoid typos/save time but some repositories may prefer to use “not dated” or “unknown.” If there could be a controlled vocab, perhaps it should be repository configurable and drop down from the date expression field? Seeking more info/feedback. I think we need more information on this one - stuff like how it would be mapped, how it works with date expression, and how any migration would work | |
Alicia | Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-538 |
---|
|
| | |
Alicia | Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-797 |
---|
|
| | |
Alicia | Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-799 |
---|
|
| | |
Patrick | Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-802 |
---|
|
| Was not able to duplicate on test.archivesspace.org using : http://test.archivesspace.org/staff/resources/45#tree::resource_45 Could use more information about specifics to trigger action. | |
Patrick | Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-828 |
---|
|
| Changing defaults seems to make sense to me as the image does look like a broken link. Should be a fairly easy switch to have a different default image. | |
Patrick | Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-557 |
---|
|
| Need more contextual information about what would "look better". Also need clarity on on the "add into the Edit Basic Information the Resource or Accession number and links back to the component". Do they just want links back to the linked resource/accession? | |
Edgar | Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-784 |
---|
|
| I have confirmed that 700 field is placed first as Creator while 110 field is second. 7xx are Contributors not Creators. 1xx are Creators. Rec: Pass | |
Edgar | Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-441 |
---|
|
| This is a strange behavior for a drop down list and adds an unnecessary extra step. Also when choosing an Agent, the behavior of that drop down is slightly different as there is a browsing feature also the X/delete is within the box and not the down arrow as with Agent Relator. Is there a known reason for the behavior or deleting the choice first? The benefit seems to be a faster way to clear out a selection. It appears that it isn’t a drop down but a complex text box with some sort of ajax autocompleter so how easy would it be to replace this with a static drown down? Rec: Probably Won’t do. | |
Edgar | Jira Legacy |
---|
server | System JIRA |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 36c489e2-4fb0-353a-985b-64038401be2f |
---|
key | ANW-455 |
---|
|
| Is this here?: https://archivesspace.github.io/archivesspace/doc/alpha_index.html If so, then this would be super helpful for developers. Rec: Pass | |