Item/Who | Notes | Decision |
|---|
Roll Call | | |
Announcements/Discussion
| How did this ticket assignment approach go? We should draft up a work plan! Sketches for a mobile-optimized view?
| Good approach; makes things easier to manage; able to discuss and send to Dev. Pri. and for final approval moving tickets forward depends on the nature of the tickets need to figure out when should a ticket “die”?
|
Tickets | | |
Lydia Tang (Unlicensed) | 1.https://archivesspace.atlassian.net/browse/ANW-785 2. https://archivesspace.atlassian.net/browse/ANW-821 | I think this is ready to go, with Ed’s comments already gone through Dev. Pri. once get input from developers/Dev. Pri so that it can move
I’ve created two resulting tickets and this one can be closed since it was to complex. How do people feel about these two tickets? https://archivesspace.atlassian.net/browse/ANW-1033 Could a check box be added to a top container instance to identify as restricted? Lydia will comment on ticket to add information about check box will need to go to Dev. Pri.
https://archivesspace.atlassian.net/browse/ANW-1032
|
Brittany Newberry (Unlicensed) | https://archivesspace.atlassian.net/browse/ANW-608 2.https://archivesspace.atlassian.net/browse/ANW-871
| I think the purpose of this ticket needs to be updated. The original issue I did not experience when testing. The ticket appears to now be about understanding how to select multiple items when using reorder mode. It’s good to know but I’m not sure how it can be resolved in the application to move forward the ticket needs to be reworked comment that did not experience issue and close ticket
I would like this feature and feel that it is similar to the generate pdf background job that used to have you reenter the resource that you were wanting to create a pdf for pass to Dev. Pri for further review consider creating a list of all tickets related to top containers for Top Container Epic to send to Christine
|
Althea Topek | https://archivesspace.atlassian.net/browse/ANW-608 2. https://archivesspace.atlassian.net/browse/ANW-350
| |
Lori Dedeyan (Unlicensed) | https://archivesspace.atlassian.net/browse/ANW-945 2. https://archivesspace.atlassian.net/browse/ANW-889
| I’ve commented on the ticket- I agree with at least one aspect of this ticket (preventing duplicate top containers) and would like to see it implemented. Consider creating warning message - Lori will follow up Lori will create a new ticket and will link and add to agenda
This looks like it is already being worked on by developers. Would just need a follow up to confirm.
|
Kate Blalack | https://archivesspace.atlassian.net/browse/ANW-477 2. https://archivesspace.atlassian.net/browse/ANW-538
| |
Julia Novakovic | https://archivesspace.atlassian.net/browse/ANW-775 2. https://archivesspace.atlassian.net/browse/ANW-552
| Viewed Jira ticket and commented; interested to hear if it would be difficult to implement, or how others have dealt with the order going from AT to AS over time. [Maybe there’s a plug-in?]
This may already be addressed with PUI in most recent releases [e.g., limiting search to collection or digital materials, vs. searching all record types]-- or am I missing something?
|
Terra Gullings (Unlicensed) | https://archivesspace.atlassian.net/browse/ANW-552 2. https://archivesspace.atlassian.net/browse/ANW-972
| I agree with Julia’s comment: I think this is [mostly] already addressed in most recent release. I agree, not sure how complicated it would be to customize per institution (though would be ideal).
|