Dec 6 - Dec 31, 2022
Report on iteration Dec 6, 2021 — Dec 31, 2021 (includes all issues completed before Jan 3, 2022).
We extend this iteration to four weeks, which included the Christmas and New Year’s holidays when most of the team was out. During this iteration, we published the second issue of Startwords and made significant progress on the Geniza 4.0 release. We have an enormous total of 41 development story points closed this iteration and a rolling velocity of 18 — this is due in part to the lengthened iteration, but also due to the significant push to complete the Geniza MVP and closing out a number of large issues (three 8-point development issues and two 5s!). We also have a huge total of 37 points (16 issues) for design work, completing the majority of the design work for the Geniza MVP. The unevenness of the design velocity likely reflects Gissoo’s observation that visual design does not fit well with an Agile development workflow, since so many things need to be designed and reviewed together.
Startwords
We completed the remaining work to publish Startwords Issue 2; work in this iteration included miscellaneous cleanup items for final publication of the essays in issue 2, and some minor cleanup work after the publication. We also started on prep work for functionality needed for issue 3, but none of those issues were closed.
Geniza
Although we postponed the 4.0 public MVP release until January, we did make a significant amount of progress towards completing the work targeted for that MVP, and we did release a 0.7 version with a significant number of updates since the previous release. Updates include improved citation formatting for footnotes and sources, revised scholarship record view for individual documents, an import of data from the PGP v3 links database (information now included in PGP v4 scholarship records), setting up Wagtail for management of content pages, and progress with interim transcription solution for synchronization from TEI to the database, including in search results, and displaying with or without images on document detail pages.
We also made tremendous progress on design: nearly all of the design work needed for the MVP has been completed and approved, and a significant amount of work was done towards implementing site visuals implement them.
New versions of djiffy and parasolr were released in support of the Geniza 0.7 release, with support for newer versions of Python & Django and improved functionality needed for the new Geniza search.
Active projects
- djiffy (0 points, 1 issue)
- geniza (78 points, 31 issues)
- startwords (0 points, 2 issues)
Releases
- djiffy 0.7 — Monday Dec 20, 2021
- parasolr 0.8 — Monday Dec 20, 2021
- startwords issue-2 — Friday Dec 10, 2021
Velocity
Development
41 points, 18 issues. Rolling velocity: 18
Design
37 points, 16 issues. Rolling velocity: 14
Closed issues by project
- djiffy (0 points, 1 issues)
- development (0 points, 1 issues)
- geniza (78 points, 32 issues)
- design (37 points, 16 issues)
- Design a homepage for the site through which users can be introduced to the project a little more and can use to navigate to other parts of the site (2) 🗺️ design
- Add styles for a header so that users can access the items in the main menu (5) 🗺️ design
- Revise the regular search results page so that tags appear at the bottom of each result + a max number of tags to appear (1) 🗺️ design
- Add a second Hebrew typeface for UI controls / labels / non-body text use (3) 🗺️ design
- Add primary and secondary colors + for light and dark variants and apply to UI components (3) 🗺️ design
- Propose styles for header, footer, navigation, form, and content components (3) 🗺️ design
- Add styles for UI components in default, hover, focus, active, and disabled states for light and dark mode 🗺️ design, Epic
- Add styles for buttons so site users can build an expectation of what its function and behavior would be (3) 🗺️ design
- Revise the type styles to ensure they are appropriate for the new typefaces (Greta Sans and Frank Ruehl) + organize them on Figma so that it's easier for the dev team to implement them (3) 🗺️ design
- Revise the logo based on the feedback received in issue #283 (3) 🗺️ design
- Add styles to the the search form components so site users can curate their search (2) 🗺️ design
- Add styles to the tab component so site users can navigate once viewing a specific document to view its details, scholarship records, and external links related to it (1) 🗺️ design
- Add styles for links so site users can identify links and check it out (1) 🗺️ design
- Add styles for pagination so users have a way to navigate between search result pages on the site (2) 🗺️ design
- Add styles for the footer so users have a way to view all the pages of the site in one place, an additional way to navigate the site, and a way to access additional links (3) 🗺️ design
- Design a footer for the site (2) 🗺️ design
- development (41 points, 16 issues)
- As a user, I want to change site language so that I can switch languages when I don't want to use the browser-detected default. (1)
- Wagtail bootstrap script doesn't work as expected 🛠️ chore
- As an admin, I want numeric footnote locations automatically prefixed with 'pp.' so the meaning of the numbers will be clear to public site users. (1)
- Look into type configuration for Percy and deploying to QA and production 🛠️ chore
- Update sitewide type to use purchased fonts, new styles 🛠️ chore
- As a front-end user, I want to see brief citations in the Document Detail view, more concise than those in Scholarship Records. (3)
- As a front-end user, I want to be able to quickly see the section a footnote is referencing in a particular source. (2)
- Reposition the tags in the regular search results so that they appear at the bottom of each item, above "view document details" 🛠️ chore
- As a content editor, I want to create and edit content pages on the site so that I can update text on the site when information changes. (8)
- As an admin, I want data from PGP v3 links database imported into the new database so that I can manage links from the main admin site. (5)
- determine how to cache local copies of IIIF manifests & set it up 🛠️ chore
- As a user, I want to see images and transcription, if any, for all fragments associated with a document so I can see the full contents that are available. (8)
- As a user I would like to see scholarship records for each document so that I can learn more about research that has been done about each document (8)
- As a user I would like to see transcription excerpts in my search results so I can tell which records have a transcription and can see some of the content. (5)
- source string method should include language if it is specified and not English 🛠️ chore
- generate a CSV of JTS IIIF manifests and DPUL view URLs from Figgy for import with new fragment url import script 🚫 wontfix
- design (37 points, 16 issues)
- startwords (0 points, 2 issues)
- development (0 points, 2 issues)