Nov 2 - 14, 2020
Report on iteration Nov 2, 2020 — Nov 14, 2020 (includes all issues completed before Nov 16, 2020).
This iteration we made substantial progress on our Geniza search prototyping, most notably implementing the first two steps towards a prototype of the holistic search interface that Gissoo has been designing.
We also made some updates and fixed some bugs for CDH web, towards a maintenance release that will go out early this iteration.
Demos
Screenshot of the experimental Geniza cluster search prototype
Active projects
- cdh-web (5 points, 6 issues)
- geniza (17 points, 8 issues)
- parasolr (0 points, 1 issue)
- princeton-cdh.github.io (0 points, 1 issue)
Releases
Velocity
Development
16 points, 13 issues. Rolling velocity: 12.33
Design
6 points, 3 issues. Rolling velocity: 4
Closed issues by project
- cdh-web (5 points, 7 issues)
- development (5 points, 7 issues)
- shift CI to github actions chore
- As an admin, I want to create staff projects that aren't R&D and have them show up on the Staff Projects page so I can highlight new work like Startwords. (0) enhancement
- As a user, I want to see PGRA profiles listed with students and postdoc profiles listed with staff, so I understand how these people relate to the CDH. (2) enhancement
- project admin edit pages load slowly, especially for large projects bug
- As a user, I want to learn about the DH Working Groups sponsored by the CDH so that I can get involved with a group that matches my interests. (3) enhancement
- unable to save changes for some items in admin invalid
- affiliate grant year ranges on profile list pages are incorrect bug
- development (5 points, 7 issues)
- geniza (17 points, 8 issues)
- design (6 points, 3 issues)
- Prototype the holistic search so that users who are exploring documents through tags, or are looking for documents by inputting search terms/keywords can navigate through the site. (3) 🗺️ design
- Revise the new search prototype so that when a search term is entered document tags are matched while showing contextual information about the clusters in which the documents appear so that the user can learn more about the position of the document with respect to the clusters (2) 🗺️ design
- Design a way to navigate to a cluster from the search results so the user can view a specific cluster and learn more about the documents it contains (1) 🗺️ design
- development (11 points, 5 issues)
- As a user, I want to search on text with or without accents so that I can easily find variants of words with accents and diacritics in the data. (1) 🧪 experiment
- As a user, when I select a topic cluster I want to browse the documents in that cluster and see their metadata and other tags so that I can explore everything in that cluster. (2) 🧪 experiment
- As a user, I want to see a list of topic clusters so I can get a sense of the major areas of content and relationships between them. (1) 🧪 experiment
- As a user, I want to search on metadata and transcriptions together so that I can find records by description or content. (5) 🧪 experiment
- As a data editor, I want metadata from the geniza spreadsheet indexed into Solr so I can run more advanced searches to find geniza materials. (2) 🧪 experiment
- design (6 points, 3 issues)
- parasolr (0 points, 1 issues)
- development (0 points, 1 issues)
- princeton-cdh.github.io (0 points, 1 issues)
- development (0 points, 1 issues)