With input from TL, I'm creating a further stage after nextFreeId which will generate a location file from data entered into a form, based on a template. The form is set up and working, and I've spent some time experimenting with embedding the template as XML into an XHTML script tag, following documentation on the MDN site, but it seems like it will be difficult to treat this data both as XML for the purposes of injecting it and as text for the purposes of doing search-and-replace to insert the data. May have to resort to generating the file on the server and returning it to the user.
Tweaked the autophonemicizer so that it applies only to phrs in cits, and then ran it on eight files ready to be done. After this was working and checked, wrote a new transformation which detects when a cit is actually a duplicate of a full entry which already exists elsewhere; comments out absolutely identical ones, and flags close ones for further checking. In this way over 1400 cits were commented out; 800+ await checking.
Received requests for website changes from LS, MH:
Undergraduate-Courses:
-new folder was created by systems and MH for Course-finder
Secondary course-finder renamed Course search
Index page: display "Course search" text
Secondary Professional writing renamed Professional communication
Home-Courses:
Secondary Professional writing renamed Professional communication
Undergraduate - future students:
-added secondary Transfer students
-reordered secondaries
-as requested: reduced number of secondaries, removed "What is English"; content to be included in next secondary listed
I now have a complete auto-markup process tuned and tweaked, and it also handles restoring (virtually all of) the lb and hi tags which are removed initially to facilitate name recognition. Very neat, and it's basically ready for testing to find out how accurate it is. I've built in some rudimentary timing too, so I'll run it tonight to see how it does.
Right now one article is outstanding from vol 22; I've done the metadata and the biblio today.
In reply to your question below about the active voice and the passive voice, and whether this makes a difference when considering whether something's an event: short answer: no.
Slightly longer answer, I don't think that we can rely on voice being translated literally and consistently enough to depend on it too much. Also, it really doesn't matter. If you can restate something in the passive in the active and you think it should be an event, than the voice doesn't matter. If you don't think it should be an event, than that should be true whether it's active or passive.
A general principle to sum up: consideration of whether something is an event should happen at several removes from any particular bit of text.
Did that help?
The per-property transaction tsv is now, I believe, complete, and we've also generated the candidate list for non-custodian transactions for SF to choose from.
We've decided on AtoM, and I've sent an email to KL, JSR and MA to get the process rolling.