Results of the 2023 Prioritization Exercise - The Lower Priorities
The following are the results of the prioritization exercise on January 18th, 2023. We drew a line about halfway down the list and determined that priorities that were above this line were the higher priorities and the ones below the line were lower priorities. That didn't mean that the lower priorities wouldn't get done in 2023, but instead that the higher priorities would be completed first.
Many times, the decision for prioritizing one idea over another was dependency – we couldn't take one aspect of the product development before another one was in place.
To recap, the priorities were created by the product team and product owner and moved to a Miro board. After all the priorities were presented, then we got to work ranking the priorities in single file order. Was this feature more important than this feature? Was the maintenance work imperative to make sure that this product was successful? This was also a time when we might uncover that some features couldn't be developed without having other priorities completed first. After all the presentations, we had a list of epics that were in priority order from the product teams.
Lower Priorities
Priorities submitted are bulleted. This is the order of the priorities as determined at the end of the prioritization process. We have grouped them for ease.
Shoreline
Finalize and cleanup ingest processes into GeoData - To be able to ingest data. Some of this is a blocker for getting any new content into GeoData.
Enable ingesting of geotiffs/raster data into GeoData - This is a significant data format. This could double the amount of content that we can ingest.
This is a significant data format. This could double the amount of content that we can ingest. - This is a significant amount of data that could be made available to users.
GeoData MVMP interface enhancements (branding, help, about, collection canned searches) - This is a requirement in order to market GeoData to our users. Brings GeoData in alignment with users' basic expectations of a discovery interface for geospatial data.
Orange Empire
IIIF Image processor authorization, upgrade/integration (kakadu) - Add a high performance image processor (kakadu) and figure how to embed the license into container images. Discuss & strategize on what type of caching solution would be best to start with.
Starlight
Fix long-standing bugs (not impacting end-users). There are a number of bug issues that have been hanging out in the backlog for a while. It would be good to get to these eventually.
Integrate Starlight and Comet - Allows us to directly publish content under Comet management to Starlight (rather than managing this content in two disconnected places). Currently all content & metadata uploaded to Starlight must be maintained separately. Also opens up the possibility of non-image or pdf object types being exhibit objects and using starlight for non-exhibit use cases (e.g., highly curated collection front-ends)
Shoreline (again)
Enable the distribution of restricted data through Shoreline - This is a significant amount of data that could be made available to users.