May 2 - May 13, 2022
Report on iteration May 2, 2022 — May 13, 2022 (includes all issues completed before May 16, 2022).
We released Geniza v4.4 early in this iteration to deliver work completed in the previous iteration, and then quickly discovered and fixed a bug with the menu button that made the site unnavigable on mobile. We did not get another release out during the iteration.
Geniza
We made progress on a number of design and development issues and both rolling velocity and iteration development work are at 6 points. This doesn’t reflect the large amount of in-progress work on transcription functionality (delivered for first-round testing but still very much in progress) and several related features around date/calendar conversion.
Startwords
No development work this iteration, but design work for issue 3 is nearly complete and editorial and design work will be ready soon for final handoff for development on the remaining items needed for completing this issue.
Active projects
- geniza (13 points, 18 issues)
- startwords (2 points, 2 issues)
Releases
- djiffy 0.7.3 — Tuesday May 10, 2022
- geniza 4.4 — Tuesday May 3, 2022
- geniza 4.4.1 — Wednesday May 4, 2022
Velocity
Development
6 points, 15 issues. Rolling velocity: 6
Design
9 points, 5 issues. Rolling velocity: 7.67
Closed issues by project
- geniza (13 points, 21 issues)
- design (7 points, 3 issues)
- development (6 points, 18 issues)
- automatically clean redundant manifest uris generated by some iiif viewers 🛠️ chore
- As a content editor, I want fragment url importing to ignore upper/lower case differences when matching shelfmarks, so that I can import urls when the shelfmarks don't match exactly. (0)
- On mobile, hamburger menu seems to overlap with the light/dark mode toggle. 🐛 bug
- As a content editor, when I'm editing a source I want footnotes sorted by location so I can review them in the same order they appear in the source. (1)
- As a front-end user, I want to see logos for museums and libraries providing image content, so I have a better sense of where the content is coming from. (1)
- As a content editor, I want the Document original date and calendar to be required together, so that I cannot produce incomplete records. (1)
- As a user, I would like to see historic and converted dates on the document details page so that I can easily find date information when it is known. (1)
- Implement the revised document detail view fields on top of the page on desktop and mobile
- Implement the search results page in RTL orientation so that the page can be read properly in Hebrew and Arabic
- Implement designs for the RTL search form for light and dark mode for desktop and mobile
- Bad Request 400 when trying to move attachments 🐛 bug
- In the admin interface, when I drop a IIIF link into the appropriate space, I get an error message. 🐛 bug
- check python convertdate library against existing structured document dates 🛠️ chore
- Implement logotype files in the header for the Hebrew site
- investigate non-transcription content in footnotes 🚫 wontfix, chore
- As a front-end user, I want keyword searches to automatically match on similar words so that I don't have to enter wildcards or multiple terms. 🖇️ duplicate
- Configuration to get fonts working in Percy 🖇️ duplicate
- As a user, I want documents that span fragments with consecutive shelfmarks to have their shelfmark displayed using a range, so that it's easier for me to read. (2) 🆕 enhancement
- startwords (2 points, 2 issues)
- design (2 points, 2 issues)
- Design for displaying content in alternate languages 🗺️ design, Epic
- Revise the language toggles so they're visually correct (2) 🗺️ design
- design (2 points, 2 issues)