2020-03-03 Meeting notes

Roll Call

Tickets

@Brittany Newberry (Unlicensed)

1. https://archivesspace.atlassian.net/browse/ANW-968

2. https://archivesspace.atlassian.net/browse/ANW-759

1. I think that this ticket should move forward. It feels like an issue that other institutions have an interest in

2. Similar to the first ticket, maybe all tickets related to component level information in the collection organization tab in the PUI should be combined and addressed. It appears that the requests reported want for at least the notes for these components to appear in the collection organization view. Need to decide if they just appear or we can choose each one based on the repository

1. send to dev. pri.

2. send to dev. pri.

@Althea Topek

1. https://archivesspace.atlassian.net/browse/ANW-608

1. I have not been able to replicate this bug.

2. I think we could move forward with this ticket.

update: I created a ticket for optimizing the mobile staff interface:

1. send to dev. pri.

2. send to dev. pri. Yes, we want a dragging capability as well.

@Lori Dedeyan (Unlicensed)

Kate Blalack

1. I was able to shift, command, click several items and reorder at once using Lydia’s instructions. This question is weirded strangely but I believe this was what the question referred to.

2. I was not able to select and transfer more than one component at a time, but I was able to use Lydia’s work around.

1. the current tickets seems of limited use and perhaps pursue the new staff ticket and create another one for temporarily sorting the public interface. Closing ticket.

2. Sounds like a bug. Reclassify as a bug and send to Dev. Pri. Limited niche but it isn’t working the way intended.

@Julia Novakovic

1. Ticket is closed!

2. Possibly a duplicate of ticket ANW-273, which is ready for implementation. Is it possible to view any mockups/wireframes for to see if that covers this request [ANW-341]?

1. closed

2. Close ticket since it was a placeholder.

@Terra Gullings (Unlicensed)

@Lydia Tang (Unlicensed)

1. I’ve asked Ed for more info

2. I personally don’t think this is a good idea. It will be too easy to create/recreate empty ghost top containers. I sympathize, especially when creating instance info for unprocessed accessions - can you realistically create 110 (for example) top containers in the database? I would like to discuss this, particularly in large-scale scenarios but my initial thought is to close this ticket.

1. Get user stories: “as a user wanting to do this, I need this” Potentially of limited benefit for others. Seeking community feedback? Cory Nimer? Maybe explore as a report, or does it exist already?

2. send to Dev. Pri. unsure about it. A more useful ticket would be to adding archival objects from the Top Container

Discussion

1. Would people be interested in spending the next two weeks exploring the Reorder mode? There are some reported bugs with it, but my main concern is the overall usability of Reorder mode. I wonder if it needs to holistically be addressed…

2. Draft 2020 work plan thoughts? Please feel free to edit and/or suggest changes!

3. Top Container pain points

1. Lydia is going to cogitate on this more to figure out a “good” plan of attack. If you have suggestions, please be in touch! We’re going to continue with regular tickets for the next meeting.

2. Work plan is looking good. We’ve covered a lot of ground! Feel free to edit/suggest changes though!

3. Top Container paint points might be another area to look into holistically for usability. Harvard will be doing some Top Container work soon, so it might be best to wait on this though.

Next meeting: March 17, 3pm ET