Helped Stew and Greg with an emergency install and configuration of the Dialang application on all the lab machines, for Marie-Josee Hamel's session tomorrow
Installed drivers for the ETCL printer, and did a trial print of the poster on 11x17 paper. Looks good. Printed two copies, and trimmed the whitespace around the edges.
I made some useful progress with the search functionality:
- All types of searches were returning multiple results, cascading through the hierarchy, and where one node contained multiple hits, it was returned once for each hit. Both of these problems are now solved; any node containing a hit is returned only once, and any exact phrase search returns only the bottom-level node containing the hit.
- The KWIC display was limited to the preceding and following sibling on an exist:match hit. This is no longer the case; it now takes the complete text of the parent, and creates a truncated intro and outtro to the hit.
- I've had a preliminary shot at thumbnails for hits on image markup annotations. I'm able to correctly retrieve the image and the dimensions, but for some reason my attempt to display only the hit area for the annotation is failing (I'm seeing a portion which is the right size, but is just the top left of the image). Nearly there, though!
The viewer search client-side functions have been enhanced. Clicking a row in the search results grid will select the Object in the tree; display the metadata; and load the Object's image, or if it doesn't have one, load its parent Object's image and highlight the Object's rectangle. The matched Objects will be marked with a different icon in the tree. On the tree toolbar are two new buttons, 'select next match' and 'select previous match', that move through the matched Object's, selecting and highlighting as appropriate. The search back end has not been changed, so it still does a boring keyword search.
In the tree, when clicking Objects with no image of their own (i.e. they are just rectangles on their parent image) - which were formerly disabled in the tree - will now load their parent Object (if necessary) and highlight the Object's rectangle.
All of these enhancements are in the online demo.
Also fixed a few messy bugs, made some icons, and was generally productive.
3. Textes tirés d’une source de documents plus grands
Quelques textes de la banque de données sont sélectionnés à partir d’un anthologie plus grande. Ceux-ci ont généralement la structure suivante :
<TEI>
<teiHeader></teiHeader>
<text>
<body>
<div>
<head>[Document title</head>
[Main body of the text]
</div>
</body>
</text>
</TEI>
Dans les cas ci-dessus, l’encodage du contenu principal ("[Main body of the text]") suit les conventions ... ci-dessous dans "Block and inline content markup".
Le teiHeader
L’élément <teiHeader> est mieux documenté par l’utilisation d’un exemple commenté accessible ici. : sample_header.xml.
Encodage d’un contenu pour arrêter et déterminer les lignes.
Block and inline content markup
Les étiquettes suivantes sont utilisées couramment dans ce projet :
*
peuvent avoir un « type attribute » / les désignant comme “chapitre” ou quelques / toutes autres divisions structurales.
* <head>: Pour les petits texts extraits / pris / à partir de plus grands documents (type 3 au dessus), le titre du texte sera balisé avec une étiquette <head>. Pour les documents plus long et isolés, l’étiquette <head> est utilisée comme des entêtes internes. L’attribut type peut être utilsé pour distinguer le type ="main" du type="sub".
* <p>: étiquette de paragraphe normal.
* <lg> et <l>: les groupes de lignes sont par défaut (be default) des strophes, et des éléments de lignes apparaissent à l’intérieur de celles-ci.
Pour des structures poétiques plus complexes (comme des sonnets), les étiquettes <lg> peuvent être insérées de façon à montrer un groupe de lignes faisant partie d’un plus grand groupe de lignes. Les étiquettes <l> peuvent apparaître seulement à l’intérieur des étiquettes <lg>. Les étiquettes <l> peuvent aussi porter un n attribut indiquant le numéro de la ligne; ceci devrait normalement être fait seulement dans les situations /cas où le texte complet du poème n’est pas inclu (en d’autres mots, seulement où quelques extraits sont balisés), pour indiquer où les lignes sont manquantes.
Reviewed draft of changes I made last week with Marie Vautier, made a few more at her request and left her with a couple of issues to decide and report back to me on.
Originally posted this on Monday Feb 26 to the wrong blog. I've deleted that posted and reposted here.
Catherine Caws and Marie-Josee Hamel want to install dialang program on all the computers in the labs by tomorrow. After some testing on one computer in lab B with Greg, it turns out we have to DL and install their own Java environment as well as their executable and jar file. Greg, Martin and I installed on all the computers in both labs.
Went back in later and figured out that dialang wrote to the program folder, which succeeds when the users is administrator but fails when the user is not. Greg, Martin and I then went back in and set the permissions on the dialang folder to allow writing by all users.
Martin and Greg posts are on Maint blog
My station was getting more and more flaky and sluggish, so I uninstalled some old stuff and did a defrag. It took a while, during which I cleaned up my desk area, a gruesome task that should be done more often.
As promised. I will be sending out a more detailed announcement to the departments on Friday. Thanks for your interest!
----------------March 16th, 1:30 - 4:30
HCMC/CALL Facility, Cle A051
The Humanities Computing and Media Centre (HCMC) is hosting its second annual project showcase.
UVic Humanities faculty and staff are recognized worldwide for their innovative use of technology in research, teaching and learning. At the showcase, they will discuss and demonstrate their projects, and welcome you to explore on your own.
A panel discussion on the pros and cons of Moodle (contrasted with WebCT/Blackboard) will also take place. Invited panelists from UVic and abroad will share their expertise, experience and opinions. The format is informal, and all are welcome to contribute to the discussion. Find out why Moodle is growing quickly as an alternative classroom management system (and how educators are using it).
To learn more about the projects and the panel discussion, visit the showcase web site at http://hcmc.uvic.ca/showcase/index.php.
Nibbles and drinks will be served.
For more information, please contact Scott Gerrity (ext. 8787, sgerrity@uvic.ca).
Attended presentation on French CALL database which went till after 6.
Lexical items of correct usage based on analysis of lexical errors made by Anglophones writing in intermediate to early advanced French (e.g. "visiter" when they mean "admitted to hospital" rather than "visiting a hospital").
Product appears to be a dictionary rather than an expert system parsing student work.
Need to find out more on: 1) if db is based on anglocentric errors, to what degree is it useful to non-Anglophones. 2) is student searching this lexical "dictionary" able to query by incorrect use or does dictionary provide information on likely constructions to avoid as well as those to use.