http://hcmc.uvic.ca/blogs/index.php?blog=34 Blog for the Colonial Despatches project en-CA hourly 1 2000-01-01T12:00+00:00 http://hcmc.uvic.ca/blogs/index.php?blog=34&title=co_60_vol_13_page_images_added_to_the_co&more=1&c=1&tb=1&pb=1 2013-05-15T17:16:21Z mholmes Announcements (Mins: 15) 1309 page images for CO 60 Vol 13 (in three different sizes) have been added to the collection. These cover the British Columbia 1862: Despatches to London. These will now be linked into the transcription documents. Mins: 15

1309 page images for CO 60 Vol 13 (in three different sizes) have been added to the collection. These cover the British Columbia 1862: Despatches to London. These will now be linked into the transcription documents. 1309 page images for CO 60 Vol 13 (in three different sizes) have been added to the collection. These cover the British Columbia 1862: Despatches to London. These will now be linked into the transcription documents.

]]> http://hcmc.uvic.ca/blogs/index.php?blog=34&title=tb_now_has_upload_privileges&more=1&c=1&tb=1&pb=1 2013-04-05T21:37:26Z mholmes Activity log (Mins: 30) Added him to the coldesp group so he can upload maps while I'm away. Reminder to self: unsigned jars bug is caused by using OpenJDK 1.6; switch to 1.7 to avoid. This is a per-user setting on the machine. Mins: 30

Added him to the coldesp group so he can upload maps while I'm away. Reminder to self: unsigned jars bug is caused by using OpenJDK 1.6; switch to 1.7 to avoid. This is a per-user setting on the machine. Added him to the coldesp group so he can upload maps while I'm away. Reminder to self: unsigned jars bug is caused by using OpenJDK 1.6; switch to 1.7 to avoid. This is a per-user setting on the machine.

]]> http://hcmc.uvic.ca/blogs/index.php?blog=34&title=collected_stats&more=1&c=1&tb=1&pb=1 2013-04-03T15:29:35Z mholmes Activity log (Mins: 20) Collected stats for the first quarter of 2013. Mins: 20

Collected stats for the first quarter of 2013. Collected stats for the first quarter of 2013.

]]> http://hcmc.uvic.ca/blogs/index.php?blog=34&title=changed_old_tapor_urls_to_hcmc&more=1&c=1&tb=1&pb=1 2013-03-28T23:16:46Z mholmes Activity log (Mins: 15) Old URLs for www.tapor.uvic.ca were being used to call on resources on the home1t filesystem; I've now switched all of those to hcmc.uvic.ca. This should also be done for other projects such as Mariage. Mins: 15

Old URLs for www.tapor.uvic.ca were being used to call on resources on the home1t filesystem; I've now switched all of those to hcmc.uvic.ca. This should also be done for other projects such as Mariage. Old URLs for www.tapor.uvic.ca were being used to call on resources on the home1t filesystem; I've now switched all of those to hcmc.uvic.ca. This should also be done for other projects such as Mariage.

]]> http://hcmc.uvic.ca/blogs/index.php?blog=34&title=added_a_favicon&more=1&c=1&tb=1&pb=1 2013-03-26T20:27:53Z mholmes Activity log (Mins: 30) Finally registered my annoyance at the presence of the Tomcat favicon, and created a little loupe-based thing based on the banner. Mins: 30

Finally registered my annoyance at the presence of the Tomcat favicon, and created a little loupe-based thing based on the banner. Finally registered my annoyance at the presence of the Tomcat favicon, and created a little loupe-based thing based on the banner.

]]> http://hcmc.uvic.ca/blogs/index.php?blog=34&title=processing_map_images&more=1&c=1&tb=1&pb=1 2013-03-14T17:53:50Z mholmes Activity log (Mins: 60) We have a large number (126) HBC images in our incoming collection. Of these TB has processed eleven, and marked up five so far. Those have been added to the maps folders, both locally on my machine (and therefore backed-up to Rutabaga) and on the coldesp account on home1t. This is documentation of how such images should be processed prior to being marked up with the Image Markup Tool. The first stage in the process is for someone to examine each image, trim it (to remove the colour bar etc.), and possibly try to enhance it, especially if it's a bit dark or murky. Next, resizing and creating the various versions. We constrain our full-size images to a maximum width of 5000 pixels; we also use images at 1000, 200, and 100 pixels (the last are our thumbnails). There is a script in trunk/utilities called process_map_images.sh which you run as follows: Copy all the trimmed/enhanced images you want to process into an empty folder. Copy the script there too, and make it executable. (The script is for Bash, and requires ImageMagick.) Run the script. It should create subfolders for each of the four sizes we require. Copy the contents of those folders into the equivalent folders where the existing maps are stored (including on home1t/coldesp/www/maps). An encoder can now get one of these images off the web server, and store it directly in the trunk folder in their svn repo (without adding it to svn, of course). Then they can clone an existing image markup file, tweak the metadata in Oxygen, then in the Image Markup Tool, delete all the boxes and replace the image. Then they're ready to start annotating. Mins: 60

We have a large number (126) HBC images in our incoming collection. Of these TB has processed eleven, and marked up five so far. Those have been added to the maps folders, both locally on my machine (and therefore backed-up to Rutabaga) and on the coldesp account on home1t. This is documentation of how such images should be processed prior to being marked up with the Image Markup Tool. The first stage in the process is for someone to examine each image, trim it (to remove the colour bar etc.), and possibly try to enhance it, especially if it's a bit dark or murky. Next, resizing and creating the various versions. We constrain our full-size images to a maximum width of 5000 pixels; we also use images at 1000, 200, and 100 pixels (the last are our thumbnails). There is a script in trunk/utilities called process_map_images.sh which you run as follows: Copy all the trimmed/enhanced images you want to process into an empty folder. Copy the script there too, and make it executable. (The script is for Bash, and requires ImageMagick.) Run the script. It should create subfolders for each of the four sizes we require. Copy the contents of those folders into the equivalent folders where the existing maps are stored (including on home1t/coldesp/www/maps). An encoder can now get one of these images off the web server, and store it directly in the trunk folder in their svn repo (without adding it to svn, of course). Then they can clone an existing image markup file, tweak the metadata in Oxygen, then in the Image Markup Tool, delete all the boxes and replace the image. Then they're ready to start annotating. We have a large number (126) HBC images in our incoming collection. Of these TB has processed eleven, and marked up five so far. Those have been added to the maps folders, both locally on my machine (and therefore backed-up to Rutabaga) and on the coldesp account on home1t. This is documentation of how such images should be processed prior to being marked up with the Image Markup Tool.

• The first stage in the process is for someone to examine each image, trim it (to remove the colour bar etc.), and possibly try to enhance it, especially if it's a bit dark or murky.
• Next, resizing and creating the various versions. We constrain our full-size images to a maximum width of 5000 pixels; we also use images at 1000, 200, and 100 pixels (the last are our thumbnails). There is a script in trunk/utilities called process_map_images.sh which you run as follows:
  • Copy all the trimmed/enhanced images you want to process into an empty folder.
  • Copy the script there too, and make it executable. (The script is for Bash, and requires ImageMagick.)
  • Run the script. It should create subfolders for each of the four sizes we require.
  • Copy the contents of those folders into the equivalent folders where the existing maps are stored (including on home1t/coldesp/www/maps).
• An encoder can now get one of these images off the web server, and store it directly in the trunk folder in their svn repo (without adding it to svn, of course). Then they can clone an existing image markup file, tweak the metadata in Oxygen, then in the Image Markup Tool, delete all the boxes and replace the image. Then they're ready to start annotating.

]]> http://hcmc.uvic.ca/blogs/index.php?blog=34&title=wrote_xslt_to_scale_image_markup&more=1&c=1&tb=1&pb=1 2013-03-14T16:47:06Z mholmes Activity log (Mins: 60) I've written some XSLT to scale the image markup for any maps which were marked up with larger-scale images than we conventionally use on the site. This may be handy in future too. I still need to do the actual scaling of all remaining HBC maps that have been added to the system. That'll have to be handled through a script. Mins: 60

I've written some XSLT to scale the image markup for any maps which were marked up with larger-scale images than we conventionally use on the site. This may be handy in future too. I still need to do the actual scaling of all remaining HBC maps that have been added to the system. That'll have to be handled through a script. I've written some XSLT to scale the image markup for any maps which were marked up with larger-scale images than we conventionally use on the site. This may be handy in future too. I still need to do the actual scaling of all remaining HBC maps that have been added to the system. That'll have to be handled through a script.

]]> http://hcmc.uvic.ca/blogs/index.php?blog=34&title=hbc_images&more=1&c=1&tb=1&pb=1 2013-03-13T23:28:55Z mholmes Activity log (Mins: 60) TB has been working on image markup, but the HBC images on which he's working aren't yet in the system. I've processed and uploaded the 11 he's picked out, but I should probably convert all the remaining ones to the right sizes too, for future use. Mins: 60

TB has been working on image markup, but the HBC images on which he's working aren't yet in the system. I've processed and uploaded the 11 he's picked out, but I should probably convert all the remaining ones to the right sizes too, for future use. TB has been working on image markup, but the HBC images on which he's working aren't yet in the system. I've processed and uploaded the 11 he's picked out, but I should probably convert all the remaining ones to the right sizes too, for future use.

]]> http://hcmc.uvic.ca/blogs/index.php?blog=34&title=built_new_oai_recordset&more=1&c=1&tb=1&pb=1 2013-02-18T19:42:57Z mholmes Activity log (Mins: 120) Regenerated all the OAI records locally, then uploaded them to the db, and provided a zip for the library to process into whatever Canadiana requires (it can't ingest OAI effectively, apparently). Mins: 120

Regenerated all the OAI records locally, then uploaded them to the db, and provided a zip for the library to process into whatever Canadiana requires (it can't ingest OAI effectively, apparently). Regenerated all the OAI records locally, then uploaded them to the db, and provided a zip for the library to process into whatever Canadiana requires (it can't ingest OAI effectively, apparently).

]]> http://hcmc.uvic.ca/blogs/index.php?blog=34&title=db_updated_and_schematron_constraints_cr&more=1&c=1&tb=1&pb=1 2013-02-06T22:17:20Z mholmes Activity log (Mins: 60) Finished uploading all the changed files to the db -- it took about five hours. In the meantime, I've started a Schematron file with some basic constraints, and shown KSW how to use it; he'll generate some more ideas for constraints from the documentation, and we'll then add the Schematron constraint to the top of the files so it's in force for everyone editing. Mins: 60

Finished uploading all the changed files to the db -- it took about five hours. In the meantime, I've started a Schematron file with some basic constraints, and shown KSW how to use it; he'll generate some more ideas for constraints from the documentation, and we'll then add the Schematron constraint to the top of the files so it's in force for everyone editing. Finished uploading all the changed files to the db -- it took about five hours. In the meantime, I've started a Schematron file with some basic constraints, and shown KSW how to use it; he'll generate some more ideas for constraints from the documentation, and we'll then add the Schematron constraint to the top of the files so it's in force for everyone editing.

]]>