Thumbnails of a few georeferenced items from the CAMEL collection.
This milestone represents several months of work. University of Chicago staff began meeting with the BTAA-GIN Product Manager in the summer of 2023 to prepare their metadata and workflows. After several rounds of iterative testing, we were able to ingest the CAMEL records in January 202- The U. Chicago staff did a great job of programmatically producing metadata in the GeoBTAA Aardvark metadata profile, and we are able to load their records without needing to perform any augmentation or edits.
Reviewed status of international Humanitarian Data Exchange portal
Worked on harmful language statement and identified the need to update our policies for accessibility, privacy, and usage.
Community Engagement
Discussing how to identify and share key documents in Google Drive, such as communication templates and reuseable graphics. Planning to set up a sprint to select these documents.
Knowledge
Distributed a member survey to identify research priorities as BTAA institutions
Reviewed the Journal of Geography and Map Libraries call for proposals related to geoportals and archiving
Coordination
Held kickoff meeting and discussed how to structure the monthly Team Meetings.
The Geodata Pilot Collection Workgroup held a kickoff meeting, where they discussed the concept of foundational layers and identified guidelines for selecting sample datasets.
The new Northwestern University Team Member attended a program orientation and began attending Team Meetings.
Our graduate student Research Assistant and Product Manager attended a Research Spike with librarians from three University of California schools. They researched OpenIndexMaps and identified areas where GeoBlacklight needs to be updated for OpenIndexMaps. We created a new GitHub Project Board to track our related plans for the BTAA-GIN.
The BTAA-GIN Executive Committee reviewed our Geodata Collection Strategic Plan, and approved our plans for next steps.
Development primarily focused on deferred maintenance and technology stack upgrade goals that improved performance and better prepares the Geoportal for future Blacklight and GeoBlacklight releases.
Improved site performance by compressing CSS and JS assets
upgraded Ruby to v3.3.0
upgraded Ruby on Rails from v6.1 to v7.0
upgraded the Mirador IIIF viewer
We also participated in the GeoBlacklight Community Sprint, which began at the end of January. Our goals are to modernize the applications JavaScript libraries, and overhaul the documentation site.
Public documentation: Teach the Team Members how to write in Markdown and contribute to our new website.
Asset management: Create a Technology Roadmap that includes Geoportal maintenance as well as the new features required by our Geodata Collection Strategic Plan.
