HCMC Blogs

This has thrown up a possible issue with ellipses and spacing. Waiting for JT's response before possibly working through all current documents to add spaces around ellipses where they're not present.

...from JT.

...from JT.

This short review has now had six sessions of entering corrections, between author's responses and the two editors. :-)

Here's how to add a static page to a site hosted in conferences.uvic.ca:

Login in conference manager
Under General Management choose System Plugins
In Plugin Management choose Generic Plugins
In Generic Plugins find Static Pages Plugin and click Edit/Add content
Click on Add New Page or Edit beside existing page
Edit content
Click the Save button

To link to that page, the URL is:
http://conferences.uvic.ca/index.php/va2012/index/pages/view/PATHFORFILE

where PATHFORFILE is specified in the path textfield in the Static pages plugin (I suspect it's really just a file name, so I'd use no spaces or punctuation in it).

First, you've got to get the finance people to create a test account for you with the beanstream service. Robert Elves has been my contact.
That account's permissions have to be set so that it has full access to the configuration / secure web space area.
You need to

The procedure for the Custom Hosted Form is described here:
https://beanstreamsupport.pbworks.com/w/page/26445713/Custom%20Hosted%20Form

The Custom Hosted Form page says "Navigate to configuration > secure webspace in the Beanstream member area and upload your files to the Beanstream server." If your account does not have permission to access that area, you'll get an error message.

You'll need to read through the API Integration pdf document at https://beanstream-manuals.pbworks.com/f/BEAN_API_Integration.pdf

I managed to succeed with the following fields in my form:
merchant_id
hashValue
errorPage
declinedPage
approvedPage

trnOrderNumber
trnAmount
trnCardOwner
trnCardNumber
trnCardNumber
trnExpMonth
trnExpYear
trnCardCvd

ordName
ordEmailAddress
ordPhoneNumber
ordAddress1
ordCity
ordProvince
ordPostalCode
ordCountry

you can see your merchant id on the home page when you log in to your beanstream account
hashvalue is discussed in the next post - it is required and is not trivial to implement
card values to use for testing are provided in the API Integration PDF file
details on all the other fields and legal values are provided in the API Integration pdf file mentioned above

Next post is on how to include a hash code (it's protected).

Approved payment for HCMC recent equipment purchase

Mainly em dashes.

Following a discussion on TEI-L, and more discussion with KT, it looks as though we should move towards the following approach:

• <rs> should be used instead of <persName> to mark up epithets in the text. persName is only appropriate for a subset of references to people (those which are actually names), while <rs> is generic and can thus be used to simplify the markup.
• Initial markup should link epithets only to <person> elements, not to their constituent epithets.
• The personography should then be re-generated from the text markup, and should encode epithets something like this:

  <person xml:id="Fred">
    <note type="epithets">
      <rs xml:id="Fred_ti">the idiot</rs>
      [...]
    </note>
  </person> 
  

  with the <note> element populated by rs elements, one for each distinct value string found in the text, with @xml:id attributes generated appropriately.
• KT should then go back through the text, and for every <said> element found (which initially would have been given @who="pers.xml#Fred", modify the @who attribute to point to the specific epithet in force at that point in the text. (This methodology doesn't specify how the decision as to which epithet is in force might be made; KT takes that decision.)
• Categories of epithets can now be created, as previously, using a <linkGrp> and constituent <link> elements.
• Ultimately, these <linkGrp> elements might be re-expressed through XSLT as <category> hierarchies in a <taxonomy> element in the header, for the sake of clarity and portability.

However, for the moment, since the serial markup is nearly finished, KT will continue with the current methodology to complete it. Then we will auto-generate a new personography, and compare it with the one she's been creating as she goes, as a sort of check on accuracy and consistency. Work on the Harper edition may then proceed based on the steps above.

Entered author's and editor's proofing corrections, and fixed several markup errors. Also noted some ambiguities in corrections; awaiting instructions from JT.