HCMC Blogs

These are the resulting plans:

• SVN and TRAC will be moved from Lettuce to a new VM. RE will take care of that by the end of November. That machine will be managed by Sysadmin, although we will have admin over SVN (creation of repos, management of users).
• Greg will check out whether the VMWare license allows the use of a VM as a member of the cluster. If this is allowed, RE will build a VM and add it to the cluster. Sysadmin will manage this VM too, along with the other cluster nodes.
• Map of London will be ported by the end of November (excepting the experimental map, which will be rebuilt by Greg and Martin later).
• Lettuce will be brought down during the first half of December, rebuilt, and added to the cluster.
• The new DB server will be purchased soon, and built up with the latest RedHat, PostgreSQL and MySQL. We shall call it Orange.
• Project data will be ported from Cress to the new DB server early in the new year.
• Chard will be rebuilt as the backup for Pear, and we will write scripts to keep it in sync.
• Cress will be rebuilt as the "warm mirror" for the new db server.
• Arugula will need to be upgraded from Redhat 4 to Redhat 5 or 6 64-bit at some point; Sysadmin will warn us in advance of outages etc.

(text-indent[\s]*:[\s]*[^;]*[;])|(text-indent[\s]*:[\s*][\d][^\s;]*$)

Leaving early for an appointment.

I've been working on reproducing the Index page and its subpages -- it's basically an index of indexes, and the subpages are sometimes hard-coded and sometimes generated automatically from the db. I've set up individual pages in /data/info for each of the subpages, which allows them to have their own introductory text, but the rendering of all, including the main index page, is handled by index_site.xql, which gets the content from the info page and merges it with data from the db where appropriate.

I've hit one stumbling-block of my own making. There were a lot of entries in the INDEX1.xml file which were defined as @type="ward" (the list is below). When these were converted over to new files in the locations subcollection, they were not provided with <place> elements because they had no location data in them (no <section> or <coords>). That means they don't have their @type attribute. I'll have to add this info manually to the 26 records, and I should also check for other records which have lost a type attribute. There are no other type attributes which are completely missing, but there are 18 street, site and church items items which didn't have proper locations, so lost their types.

ALDE2
ALDG2
BASI1
BILL2
BISH1
BREA3
BRID3
BRID4
BROA3
CAND2
CAST2
CHEA1
COLE2
CORD1
CORN1
CRIP2
DOWN1
FARR1
FARR2
LANG1
LIME1
PORT1
QUEE3
TOWE4
VINT2
WALB2

Four timesheets completed and put in the mail.

A slightly expanded version of the list of features AY wants in the administrative tool for Philosophy in Review, which I blogged here (http://hcmc.uvic.ca/blogs/index.php?blog=14&p=8672&more=1&c=1&tb=1&pb=1), mistakenly in the wrong blog.
- associate a book with a book-review-author and inform book-review-author, set deadline for receipt of review
- report those book-reviews that have been assigned but not received shortly before deadline, at deadline, after deadline and ideally automatically send out reminders to book-reviewer
- allow book-review-author to upload review and automatically inform editor
- allow editor to assign a review to review-reviewer(s) and set a deadline for review of the book-review
- send book-review anonymously to review-reviewer(s)
- report those review-reviews that have been assigned but not received shortly before deadline, at deadline, after deadline and ideally automatically send out reminders to review-reviewer
- allow review-reviewer to submit comments to a repository where editor can view them
- allow editor assign judgement of "accept", "reject", or "request revision" to book review, facilitate or automate send message to book-review-author, easily include comments from review-reviewers
- allow book-reviewer to submit updated review and allow editor to iterate through review and judgement cycle

I sent this off to IK in the library as it seems that the OJS admin tools might do enough of this that we can't justify the time to write a new tool.

Submitted a FAMIS report requesting the flickering lights in CLE -B043c be replaced again.