MAJW 2023-05-29 to 2023-06-02
to : Martin Holmes
Minutes: 320
On Tuesday, met with AB to plan out the next few weeks. Key points and action items for me, which must be dealt with in the next two weeks, at which time we’ll get together with the RA and begin working out detailed workflows and documentation.
- Ids for terms should be meaningful, and the
<event>/@periodattribute should be constrained to only those. - Ids for relationships should be meaningful, and the
<ptr>/@anashould be constrained to e.g.rel:brother. - The
<relation>element needs@resp, so that assertions of relationships can be made based on expertise; it should be constrained to the team’s identifiers. - We need a What’s New page, anticipating a fall release ahead of SSHRC adjudication.
- We need a taxonomy of objects mentioned in records (books, clothing, etc.). AB will provide this, but I can get started with those two items for now. They will need to be associated with events somehow.
- Events need to be split out by year, just as prosopography items were split by initial letter.
- We need a way to signal that entries are unproofed or provisional (people and records), so the RA can enter data and then AB can review.
- We need automated code as in DVPP linkGrps to provide the next appropriate id for person and event records.
On Thursday, split out all the events by year, and tweaked the rendering so that the build still works. This appears to have worked well.
On Friday, implemented more of the normalization and standardization from last week’s plan, as well as a next-id-is Schematron rule for events; prosopography entries need a similar thing.