-
Notifications
You must be signed in to change notification settings - Fork 1
Roadmap
Olin API began as a project in Hacking the Library Spring 2017 at Olin College.
After a few weeks of work, here's how it was presented (protip: that won't make much sense without the speaker notes).
So: where do we go from here? This roadmap is intended to be a living document that codifies the direction and goals of the Olin API project.
Each API component is categorized (for now - living document!) as either explore, create, or sustain. Projects in explore are still being designed and thought through - how should this be done? Should it even be done? Who would use this? How? Projects in create are under active development, and not yet ready to be used by the world. Projects in sustain are live and (hopefully) being used! That doesn't mean they don't have bugs that need to be fixed and improvements to be made, though.
Olin-API provides programmatic access to the rich digital life and resources of Olin.
Summary
Protect the API itself by ensuring a standard of honorable use, responsible development, and application stewardship. As a bonus, enable discovery of applications which use the Olin API.
Status
Create
Summary
Enable users to easily prove that they are a member of the Olin community, and more specifically who exactly they are. Enable application developers to write applications available only to the Olin community and protect users with a minimum of effort.
Status
Create
Summary
Provide access to data and metadata about Olin community members. Everything at Olin is done by people, so it’s probably valuable to keep some records!
Status
Create
Summary
Provide storage for documentation and descriptions of projects undertaken at Olin. There’s no centralized repository for projects, and sometimes students or faculty would like to reference older projects but no longer remember where they were stored/what they were about.
See https://github.com/MatthewBeaudouinLafon/Project-Projects
Status
Create
Summary
Provide simple access to historical and real-time email data from Olin’s mailing lists. While email archives exist, the database should be more easily searchable while being equally easy to access.
See https://github.com/aloverso/heartbot and https://github.com/aidankmcl/CarpFace
Status
Explore
Summary
Accumulate a collection of question-and-answer data from the Olin community, including metadata enabling it to be usable in automated knowledge systems.
Status
Explore
Summary
Enable simple queries of Olin’s library resources.
See https://github.com/DakotaNelson/bookbot and https://github.com/aloverso/loanbot
Status
Explore
Summary
Provide a central event database for the Olin community.
Status
Explore
Summary
Enable access to Olin’s digital signage resources.
Status
Explore