HCMC Blogs

Loading speed was very slow because the JSON for locations took time to generate, so I've moved that process offline; it now runs as part of the utilities/createGazetteer.xsl file, and generates two new JSON files (one for categories, one for locations) in the db/generated folder. That speeds everything up.

I now have the GUI for locations and categories working as I want it to, so that checking and unchecking both categories and locations is coordinated and shows the proper state to the user. Next step is converting coords to proper feature coords for OpenLayers.

In previous post, I described what I did to get a link on the About Page to a page in my plugin containing the Open Review Policy (as generated by the journal admin on the settings page of the plugin).

This post is on creating the Open Review Policy page.

In the OpenReviewHandler.inc.php file, added this function

function openReviewPolicy($args, &$request) {
$router =& $request->getRouter();
$journal =& $router->getContext($request);
$openReviewPlugin =& PluginRegistry::getPlugin('generic', OPENREVIEW_PLUGIN_NAME);
$templateMgr =& TemplateManager::getManager();
$templateMgr->assign('pageHierarchy', array(array($router->url($request, null, 'about'), 'about.aboutTheJournal')));
$templateMgr->assign('openReviewPolicy', $openReviewPlugin->getSetting($journal->getId(), 'openReviewPolicy'));
$templateMgr->display($openReviewPlugin->getTemplatePath() .'/openReviewPolicy.tpl');
}

Obviously the last line tells the TemplateManager instance which smarty template to use (see below). I'm not quite sure what each of the arguments in the second-to-last line does. Also, nowhere in the whole chain does the Locale variable for the actual policy get invoked, but the text appears on the page - that makes no sense to me.

Here's the working script of the openReviewPolicy.tpl file:

{strip}
{assign var="pageTitle" value="plugins.generic.openReview.settings.openReviewPolicyTitle"}
{include file="common/header.tpl"}
{/strip}

To add a link to Open Review Policy page in the plugin at the end of the policies section of the journal's About page:

added to OpenReviewPlugin.Inc.php

in the register() function

HookRegistry::register('Templates::About::Index::Policies', array(&$this, 'addOpenReviewPolicyLinks'));

function addOpenReviewPolicyLinks($hookName, $args) {
...
$output .= '<li>» <a href="'. $templateMgr->smartyUrl(array('page' => 'openreview', 'op'=>'openReviewPolicy'), $templateMgr) .'">';
...
}

the value of the "op" argument (openReviewPolicy) is the name of the function in OpenReviewHandler.Inc.php to invoke on launching the page whose name matches the value of the "page" argument (openreview).

Following some work and discussion over the weekend, I've added Wiggins, DEEP and DOI to the @type attribute for <idno>; changed mdtEncyclopediaLocationGeneric to mdtEncyclopediaGeneric; changed the <catRef>s of two documents that were in this category; regenerated the schema; and updated the data on the live site.

The server is now too paltry to manage the generation of a spreadsheet from our title data without timing out or running out of memory, so after setting all owners identified as definitely Japanese to Japanese ethnicity, I wrote some XSLT to generate a spreadsheet of title data for titles related to the Custodian, and forwarded this to SF.

Set out to add a heading and text area for open review policy to the settings page in the openReview plugin:

in classes/form/SettingsForm.inc.php

add these lines to assign a volue for the contents of the text area

$this->setData('openReviewPolicy',
$plugin->getSetting($journal->getId(), 'openReviewPolicy') ?
$plugin->getSetting($journal->getId(), 'openReviewPolicy') :
__('plugins.generic.openReview.settings.default.openReviewPolicyDescription',
array('journal' => $journal->getLocalizedTitle()))
);

add this to readInputData() (not sure exactly why)

'openReviewPolicy'

add this line to fetch() to assign the value of the second argument to the element in the DOM specified by the first argument

$templateMgr->assign('openReviewPolicyContent', __('plugins.generic.openreview.settings.default.openReviewPolicyDescription'));;

add this line to execute() to write the value of the element in the DOM with the id specified by the third argument and the key provided in the second argument to the plugin_settings table in the db
$plugin->updateSetting($this->_journalId, 'openReviewPolicy', $this->getData('openReviewPolicy'), 'string');

in templates/seetingsForm.tpl

add these lines to create the elements in the DOM to display and edit the text of the open review policy
<h4>{translate key="plugins.generic.openReview.settings.openReviewPolicyTitle"}</h4>
<textarea name="openReviewPolicy" id="openReviewPolicy" rows="12" cols="80" class="textArea richContent">{$openReviewPolicy|escape}</textarea>

Tried to add a link to an open review policy page at the end of the list of policies in the Journal/About page

in OpenReviewPlugin.inc.php

add this line in register()

HookRegistry::register('Templates::About::Index::Policies', array(&$this, 'addOpenReviewPolicyLink'));

add a callback function

function addOpenReviewPolicyLinks($hookName, $args) {
...
$output .= '<li>» <a href="'. $templateMgr->smartyUrl(array('page' => 'openreview', 'op'=>'openReviewPolicy'), $templateMgr) .'">';
...
}

Which successfully generates a link with the correct link text at the bottom of the policies section of the about page for my journal to the url http://hcmc.uvic.ca/people/stewart/ojs-github/ojs/index.php/slatest1/openreview/openReviewPolicy
but when I click on that link I get a 404

You want to build a website featuring the artefacts provided by Holocaust survivors. There are about 20 such people in your project and each of them may provide one or more of each of videos, audios, images, texts.
The site will consist of :
a page for each subject with
- their name,
- their photo,
- possibly bio details provided by project,
- presentation of each artefact associated with that person
- possibly a map with places significant for this person highlighted
a home page
an about this project page
a listing of the people - each a link to that person's page
a map with at least one dot for each person showing a significant location
possibly a table of contents by media type, with each entry linking to the associated person's page

This material will be independent of any copies of the same material held by the library in DSpace.

On occasion, additional people and artefacts may be added to the archive.

In the future, the project may want to develop educational materials based on the archive. That's a separate project, but should be kept in mind in making decisions about organization and identification of documents etc.

I have a sampling of artefact documents (images, videos etc.).

I'll sketch out a plan for the organization of files, necessary metadata etc. to support the desired capabilities and Graphic User Interface.

Building a detailed implementation plan for the change whereby @resp and @cert become global.