-
Notifications
You must be signed in to change notification settings - Fork 11
IIP Roadmap 2017 Spring Summer
For 10 weeks in summer 2017, there will be 5 iUTRA students working on various aspects of IIP. They will begin their work by implementing the new IIP features that are laid out in Elaine Froelich's wireframes. The wireframes do not provide a completed design, but are intended to be used as a set of new features and interactions.
It seems easiest and most effective to continue to work in Django, although we will create a new, clean install for the student work.
- Map search view (map and interface)
- Blog/news
- Stories
- Inscription of the day
- Social links
- Commenting feature
- clean up current code base, getting rid of old cruft (not necessary for student work, but should be done and will contribute to the cleaner files we want them to work on) [Carlos, Birkin]
1.a documentation?
- Make new, clean repo that focusses on viewing IIP data. We will continue handle admin things in the current repo, such as proofreading and re-indexing, for now. However we don’t want to copy those) [Birkin, Carlos; wait for feedback from Jean, Joseph]
2a. Carlos/Joseph modify API so it will permit cross site linking. This will allow the student site to use the live index or provide copy of frozen index. [Carlos]
2b. Create and document a new dev environment for students ?[Birkin, others]
-
Decide which server the live code should be on. One suggestions is the CDS server (pcdscit.services.brown.edu) which is not behind a firewall and is not a library dev/prod server. This might make it easier for students to handle frequent pull requests. EM needs to mail Joe M. and Jean R. to ask about the server. [Jean, Joseph, Birkin]
-
Workflow: Ideally the students will develop locally. Need to determine who handles pull requests (Birkin? Carlos in June?) touch base with Jean to make sure she is ok with workflow. [Jean, Joseph, Birkin]
2nd week: Ask students to make static pages using current API, and to implement some of the new interface features. This will familiarize them with the API and let them test out some of the new design features. The wireframes are not intended to be final specifications, so there will be some experimentation involved.
check where indexing happens, make sure that indexing xsl is part of resources dir on git. It should be. EM
© Brown University Library, Program in Judaic Studies