Establish a clear approach going forward with the project.
Proposal: set teams and a team lead, shorten the timeframe for drafting specifications, discuss two-three Topics a week, aim to distribute the recommendations to the ArchivesSpace community by October 24.
JIRA process: Someone submits an issue; program staff receives it; development prioritization group reviews it and makes sure there's enough info for a developer to work on, and assesses if it's something to be worked on
Created a shortlist on the rapid board. Tickets that are ready to move forward
Things to consider moving forward:
Look at the Visual-Mobile Interface document in google drive folder
Investigate alternatives to scrolling in staff interface.
Split screen? Look at Archon, AT for inspiration
User login
Within specifications, something as simple/low-tech as printing out and drawing over is helpful for developers
User accounts and permissions document.
Functionality document
Search Facets. How much information is required and helpful (or not helpful). How can we integrate elements from public interface into staff interface
Deadlines? For January or September or ? release?
Combine all specifications by end of October. Give an opportunity to discuss several topics per meeting. Have 2-3 topics to discuss per meeting
Each group can expand on their documentation. Present to the group they have, and bring questions ot the group.
Starting with next meeting, we will have 3 topics to discuss. And cycle through with end goal of October.
Expect a major release to come out in September and another in December. Thinking that most of Staff Interface won't happen until next year. Starting to put the recommendations together by October, but has to go out to the membership to review. But if there are some that absolutely has to get done or it's so obvious the pre-work is ready, then yes!
But to get things into September, window is closing. September release includes added functionality worked on outside of the program (Assessment and EAD3). If there are a couple tickets that are easy enough that a developer can work on relatively quickly, then possible.
December release, the sooner you can get thing sto us, the better. But end of October time frame would work for tickets as well. Could give enough time for prioritization overall and assign to a developer. However, a huge overhaul won't be done for December. But smaller things are possible.
No template currently. But include any wireframes or screenshots of what you would like to be is super helpful.
Granularity of Archon. If you have access to other systems and have ideas on what is missing in ASpace, please include!
Reviewing tickets
Action items
Lydia Tang (Unlicensed) to update groups to make sure people are in the group they want to be in – to do
