We have been discussing removing the duplicate entries from the database, and agreed that this is the best thing to do.
In case we change our minds in the future, I hereby record that the SVN version number before I started removing duplicates was: 136.
This is the basic plan:
PhpMyAdmin will be installed on the cluster, removing that dependency on Lettuce. This should happen soon.Subversion (replacing Lettuce in this role). This can happen basically any time, with only brief downtime for Subversion. We'll end up with a more suitable machine for the NFS role.Francotoile and MapOfLondon eXist instances need to be run on Pear, where each will run on a different port. The code itself lives in home1t, which Pear mounts, so that shouldn't be complicated, but each project is slightly different (MOL runs the full Cocoon instance, whereas FT just runs the DB). We need to decide the ports first; RE will open up those ports to the cluster in the ACL. Then we shut down the instances on Lettuce, and start them up again from Pear. Once we confirm that both projects run OK, Lettuce will be cleared for a rebuild.webserver.hcmc.uvic.ca, but we will also have mustard.hcmc.uvic.ca, lettuce.hcmc.uvic.ca and arugula.hcmc.uvic.ca access so that we can test and debug issues we might suspect with specific machines.As our funding for this phase comes to an end, here is a list of what I'll need to do in the next phase.
-Go through the rest of the list of duplicate xml:ids (duplicate_ids.ods), and merge or remove duplicate entries. (It's probably better to do this file by file, as we finish editing each alphabetical file.)
[Update, 15Nov11: What I meant by the above is that this task will be ongoing as I edit each file! It does not all need to be done before going back to editing the alphabetical files.]
-Finish editing qw-glot.xml
-Enter the Particle file cards to particles.xml (being careful not to create more duplicates!) See the blog entry from 17Mar10:
http://hcmc.uvic.ca/blogs/index.php?blog=10&p=6350&more=1&c=1&tb=1&pb=1
-Lexical Suffix files:
--replace R with ʕ or ḥ as appropriate
--check lex-suf.xml against the Lexware printout
--edit lex-suf-nom.xml
--enter missing Lexical Suffixes (check back through the file cards, as it appears not all of them have been entered); enter just the suffixes, not the example words
--have the example words that are names of people been entered as words? If not, enter them.
--phonemicize the dictegs
-Phonemicize the dictegs in the affix files
-Continue editing the rest of the alphabetical files which currently have status ="unedited". Do k, n, s, and t last, as these files contain many duplicates!
Meanwhile, Ewa is working on:
-additions to the affix files per blog posts 1-4Mar10
-go through affix paradigms to determine which ones still need entries; create entries for these affixes
-edit pron.xml and add feature structures
-proofread h-phar parts 1 and 2
Leaving a little early.
Long way to go yet, but that's already more than one abbreviation per document in the collection, on average.
Logging time spent backing up various mySQL dbs (I do this regularly, but don't usually log the time).
Another relatively straightforward one. Regexp:
(?<!abbr>)([Rr])(ec?<hi rend="[^"]+super+[^"]+">d\.?</hi>\.?) <choice><abbr>$1$2</abbr><expan>$1eceived</expan></choice>
Very common, especially in the name of the HBC. Preceding components of that name display remarkable variation, so most of those will probably end up being done manually. Regexps:
(?<!abbr>)([C])([o]?<hi rend="[^"]+super+[^"]+">y\.?</hi>\.?) <choice><abbr>$1$2</abbr><expan>$1ompany</expan></choice>
Done with regexps:
(?<!abbr>)([Dd])(esp<hi rend="[^"]+super+[^"]+">h</hi>\.?) <choice><abbr>$1$2</abbr><expan>$1espatch</expan></choice>
This is common, and I suspect there may be other variants I'll catch later on. This is the regexp:
(?<!abbr>)([Ww])(<hi rend="[^"]+super+[^"]+">h\.?</hi>\.?) <choice><abbr>$1$2</abbr><expan>$1hich</expan></choice>