Product Ownership and Guiding App Development
Bridge Development Team with Institute Stakeholders
Stay abreast of Institute priorities to determine opportunities for app improvement. Communicate stakeholder desires to developers and translate technical considerations or limitations to stakeholders. Account for ample time for developer maintenance of the site.
For large projects, ask developers to create a wiki page to track their research stage. See, for example:
New Projects: Submit a ticket on GitHub
When new software functionality is desirable or in need of improvement, create an ‘Issue’ on GitHub. To create an Issue:
Sign in to GitHub (request an account through the IT support ticketing system).
https://github.com/sciencehistorySelect the repository scihist_digicoll from the landing page.
Choose the Issues tab on the top bar.
In the green icon on the right side of the screen, select ‘create issue.’
It may also be beneficial to view previous GitHub Issues to note ongoing progress or previous attempts in updating the site.
Weekly Tech Team Meeting:
The technical team (Digital Collections Librarian, Developers, and IT director) meets weekly on Mondays at 11 am. The goal of these meetings is to review completed tasks from the previous week and prioritize tasks for the week ahead. The DC Librarian should ask for clarification of tickets at these meetings, and make decisions as necessary.
The team currently uses ZenHub to manage GitHub tickets. The Digital Collections Librarian should monitor and organize the board based on Insitute priorities. Tickets in the Inbox column should be moved either to the “ready” column or the “backlog” column in a timely manner.
Troubleshooting in the DC
Errors should be reported to the technical team as soon as they occur. A GitHub ticket may ultimately be necessary, but Slack is a good place to alert the team of errors when they first occur.
If there appears to be an error ingesting files to the digital collections, you may monitor changes or errors by selecting the ‘Job Queues’ link located in the left-hand menu of the Digital Collections dashboard.
The Job Queues board will display actions in progress. By selecting the ‘Failed’ Tab, view the most recently failed jobs and discern if the error you are experiencing has been registered by the system.
If an error does not appear in the Failed Jobs display, refresh the browser and give assets a moment to load. Some assets can take up to ten minutes to fully ingest.
If an error does appear in the Failed Jobs display or does not regulate itself after a moment, contact a software developer.