Feb 7 - Feb 18, 2022
Report on iteration Feb 7, 2022 — Feb 18, 2022 (includes all issues completed before Feb 21, 2022).
This iteration our focus was entirely on the Princeton Geniza Project as we worked to address issues identified in the 4.0 release that we wanted to address before switching the site to the official https://geniza.princeton.edu url (which we did on Thursday!).
Notable work completed in this iteration includes:
- completion of design work on the new logo and logotype (shown below), which will be integrated into the site this week.
- search results now include image thumbnails when available
- an admin document merge function, so that duplicate documents and joins can be merged manually in the admin site instead of relying on spreadsheets and script to handle merging (we discovered the script method was error-prone since merging needs to be done carefully).
Our rolling velocity for development is 13 points; this iteration we completed 19 points (16 issues).
Demos
Completed designs for new PGP logo and logotype Screenshot showing PGP search results with image thumbnails
Active projects
- geniza (35 points, 21 issues)
Releases
- djiffy 0.7.1 — Wednesday Feb 16, 2022
- djiffy 0.7.2 — Wednesday Feb 16, 2022
- parasolr 0.8.2 — Monday Feb 7, 2022
Velocity
Development
23 points, 16 issues. Rolling velocity: 17
Design
12 points, 5 issues. Rolling velocity: 6.67
Closed issues by project
- geniza (35 points, 21 issues)
- design (12 points, 5 issues)
- Design the search form for the Hebrew version of the site (1) 🗺️ design
- Design the site header and main navigation for the Hebrew version of the site (2) 🗺️ design
- Revise the PGP logo so that spacing between the letters and lines are fixed (3) 🗺️ design
- Revise the logo so that the container fades more smoothly into the header container and the "PGP" is more visible. (3) 🗺️ design
- Adjust the PGP logo for mobile (3) 🗺️ design
- development (23 points, 16 issues)
- As a frontend user, I want my search terms to match variant forms of the words I enter so that I can find all related content. (0)
- As a content admin, I want to search for documents by transcription content so I can work with and export content based on transcription text. (0)
- As a content admin, I want to see multiple transcriptions arranged horizontally, rather than vertically. (0)
- Indexing breaks with a bad IIIF URL or when the request otherwise fails (1) 🐛 bug
- As a front end user, I want to see all transcriptions expanded by default when viewing a document. (0)
- As a content admin, I want to be able to see which transcriptions belong with which footnote. (0)
- As an admin, I want to configure which languages are available on the site without disabling them in the admin site, to avoid people accidentally receiving a partially-translated version of the site that isn't ready. (3)
- setup google analytics 🛠️ chore
- As a content editor, I want to a way to add hebrew descriptions of documents to the document record, so that available information can be managed in the same place. (3)
- As a researcher, I want to see Goitein's unpublished editions labeled more clearly, so I'm not confused by the ambiguous title "typed texts". (1)
- As a content editor, I want to be able to separately define alt text and caption for images in Wagtail. (3)
- As a content editor, I want to be able to underline text in the Wagtail CMS. (1)
- As a front-end user, I want to know which specific data are associated with each attribution, so that I am not confused by a list of attributions at the end of a transcription. (1)
- increase footnote source field site in document detail view so the names and titles don't get cut off (0)
- As a user, I want to see image thumbnails with search results when available, so that I can quickly see which records have images and what they look like. (5)
- As a content editor, I want to merge document records without losing data so that I can combine records when I've identified duplicates or joins. (5) 🆕 enhancement
- design (12 points, 5 issues)