HCMC Blogs

In our usual weekly meeting we talked about a few things including the common font-style: italics typo, which I added a Schematron rule for; the asterisk line encoding pattern, which was hastily conceived by me and basically silly, so I've replaced it with a saner and more extensible approach, with changed rendering; and various issues with rhyme. I also fixed a bunch of first-line issues in the db, and re-worked the diagnostics which discovers those problems so that it doesn't trigger on anything like as many false positives; and I rebuilt the TEI for Once a Week, which has lots of new content. 210 minutes.

Worked with TEH a lot today on the FO rendering, and found a workaround for the problem of floats in forme works. I've tested a better encoding method for the situation where catchwords appear on the same line as signatures, using negative margins instead of floats, and it works well, so if JT can't see any reason against it, we'll implement that.

I also changed thousands of list type="bulleted" to list rend="bulleted", to conform with current TEI -- need to look out for fallout from that -- and put the redirects file into the XML processing pipeline so that it's available for building the id listing page, so that people don't accidentally re-use an already-obsolete id.

180 minutes.

The markup for the ancient city of Sparta is close to finished. Roughly 3 paragraphs remaining in chapter 18 book 3. After this Pausanias moves on to talk about structures in other towns in Messenia. Hopefully we can find a decent source, if not then perhaps just placing the structures in the general city location will suffice for the remainder of book 3, which ends on chapter 24. Sparta was the more important one to markup in detail and some resources are available to help identify more accurate locations. 

Continued up to 3.17.3. The eastern and southern section of the ancient city of Sparta have been mapped with coordinates. Currently working on the acropolis and structures that resided on or around it. I will attempt to finish the city with my remaining hours so that no one has to jump into an overly complicated mapping project. Hours worked :5.5 

Finished the JJE and passed it to SA. Another long and painful process. 120 minutes.

Redid my CV and attachments for this application. Long and painful process. 180 minutes.

I've spent a while working on a user-management strategy. Here's what I've come up with.

CGWP will not in any way manage or store passwords for accounts. We will retain only publically-accessible information and rely on ORCID to provide authentication. Users will require an ORCID account to become a contributor.

CGWP is a registered app at ORCID, and is allowed to use the API. Using ORCID examples I have a system that works like this:

1. users click a log-in link, which shuffles them off to ORCID to sign in.
2. Once signed in, ORCID returns them to a CGWP page that checks that they are a CGWP user and gets a responsibility parameter for their account. This is then used to allow access to, for e.g. the editor.

I am currently working on the last issue wherein ORCID's logout mechanism isn't working for me. I have a test here. Next is to finish off the editor.

I made a lot of progress today, getting used to how the Rhino engine works with the Oxygen API, and I now have two working actions with linked interface components (toolbar buttons and menu items) which allow you to add tags and also to clear tags from an entire selection. I've also added icons for these, and I've worked on the CSS for the Author view so it's easier to tell what tags in the text represent, by hovering over the curly brace representing the start tag. I think we now have a proper working environment for rapid tagging. The next stage is to have some usability testing done by HCMC folks, who in any case need to tag their texts. 360 minutes.

The main front page and the Maintenance blog have been tweaked to be a little more useful. Most blogs have not been tweaked and look a bit rubbish. Here are the changes I made. I made it as terse as I could, but they're still kind of clunky.

------

1. Log in to blogs. Toolbar at top->Site->Site Dashboard
2. Select Blog (now called a Collection) from list
3. Look for a row of tabs with titles like 'Collection Dashboard', 'Contents', 'Comments' etc. Select 'Skin'
4. Look for a section titled 'Header Top Settings'. Uncheck 'Display Header Top'. This disables the weird listing of blogs at the top of the page.

5. You can also change some of the colours used for this Collection. The main page and the maintenance blog use the following colours:

   • General Settings section: 'Color Scheme'=#005493
   • Main Header Settings section: 'Site Title Color'=#ffffff; 'Menu Links Color'=#ffffff; 'Main Header BG Color'=#002754
6. There is a save button at the bottom of the page.

7. Next, go to the 'Widgets' tab. We'll be deleting some widgets - in some cases we'll empty sections completely.

   • 'Item Page' section: Seen by, Item Vote
   • 'Item Single' section: Item Location, About Author, Seen by
   • 'Menu' section: Pages, Link to: Collection owner contact form, Link to: Log in form
   • 'Page Top' section: All blogs
   • 'Register' section: Register, Content Block
   • 'Sidebar' section: Random photo, XML Feeds
   • 'Sidebar 2' section: remove everything
   • 'Login Required' section: Log in to your account
8. We'll be editing/adding some widgets too.

9. In the 'Menu' section we'll make the 'Home' link in the header point to the front page of the whole blog system instead of the Collection front page and create a log in link that does not cause confusion.

   • 'Edit' the Link to: Front Page widget and type 'Home' in the "Link text" field. Change "Collection ID" to 1. Save.
   • 'Edit' the Link to: Log in form widget by changing 'Link Type' from "Log in form (disp-login)" to "Go to any URL", type 'Log in' in the "Link text" field, and type 'https://hcmc.uvic.ca/blogs/index.php?disp=login' in the "URL" field. Save.
10. In the 'Sidebar 2' section we're adding a widget called "Public collctions list" - you'll find it at the bottom of the widgets list under 'Other'. Leave the settings alone.

Oxygen JS gnarliness.