It looks like it's going to be most effective to create our locations as features on layers, rather than to push complete SVG layers out onto the map directly. I've been playing around with creating features this morning using pixel-based polygons, and it works well. I've also begun designing the API. The simplest approach would seem to be to provide the data in JSON, but with embedded HTML for the abstracts. Note this page for tips on escaping. The JSON can be used to construct and populate a large data structure from which features can be shown and hidden on the map, and popups can be populated as appropriate.
November 21, 2014
Logging work time spent on the TEI Council meeting at Duke in North Carolina: three work days plus one travel day = 28 hours =
November 20, 2014
I've finally got the example plugin working.
It turns out that there has to be a record in the versions table in the mysql database for the plugin. (http://pkp.sfu.ca/support/forum/viewtopic.php?f=9&t=7386) The values for that record are conventionally stored in a version.xml file in the root of the plugin. What wasn't clear to me at first is that xml file is read only when the plugin is installed or upgraded using the OJS installer/upgrader mechanism (i.e. it is not read at any other time). So, if you're building the plugin (rather than deploying one already built as a .tar.gz file), you have to add the record in the versions table manually (I used phpmyadmin).
The xml file I created (not that it's actually been read by OJS yet)
is below.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE version SYSTEM "../../../lib/pkp/dtd/pluginVersion.dtd">
<!--
* plugins/generic/dataverse/version.xml
*
* Copyright (c) 2013-2014 Simon Fraser University Library
* Copyright (c) 2003-2014 John Willinsky
* Distributed under the GNU GPL v2. For full terms see the file docs/COPYING.
*
* Plugin version information.
-->
<version>
<application>example</application>
<type>plugins.generic</type>
<release>1.1.1.0</release>
<date>2014-11-18</date>
<lazy-load>0</lazy-load>
<class>ExamplePlugin</class>
</version>
Here are the field names and values in the record in the versions table I manually entered in the db (but which presumably would be added/modified by the installer/upgrader mechanism).
major 1
minor 1
revision 1
build 0
date_installed 2014-11-18 10:40:33
current 1
product_type plugins.generic
product exmaple
product_class_name ExamplePlugin
lazy_load 0
sitewide 0
Now I've got to start figuring out how to get the plugin to actually do what I want it to do, which is a lot more complicated than writing a link into a page.
Had Greg look over it for syntax and typos and to confirm settings in php.ini and config.inc.php were correct.
Spent a couple of hours reviewing the plugin code. Disabled a bunch of other plugins to see if there was conflict. Searched entire codebase for other plugins with listener for same event as used by sample plugin to see if they were swallowing the event. No luck.
Shawn sat in for a bit and we tested various things by inserting die() statements to see exactly which bits of code were being executed and which weren't. Confirmed that the plugin is being registered, and that the event is never caught. Also checked the page throwing the event to make sure it was throwing exactly the event that we're looking for. No luck.
More searching on the user forum indicates that I have to include an entry into one of the tables in the database. That information is usually stored in an xml file in the plugin, but not yet sure how OJS gets that information from the xml file into the db. That's next
November 19, 2014
Markup for il bk 17 up to .355. A bunch of place and name conflicts. See Periphas and Hippasus posts. 10am-2:30pm = 4.5 hours
I came across the same problem as before with the Periphas missing _1 but this time it was Hippasus missing _1 there are now 4 hippasus and they each have an _#.
Would you like me to change Apollodorus 1.9.16 and 2.7.7?
In Iliad bk17.319 there is a character Periphas which was marked up incorrectly in the Characters file (without the _1) which causes me to question whether or not the text is taking about Periphas the son of Egyptus, Periphas the son of Ochesios, or Periphas the son of Iphitos.
The changes I made to fix it based on my research:
I have added the _1 to the original Periphas. Changed Apollodorus 2.1.5 to connect.
I have added periphas_3 and connected it to Il bk 17.319.
Connected Epytos of il bk 17.319 to Iphitos.
When we come across mistakes in Apollodorus should we change them or leave it?
November 18, 2014
Got just over 100 archive section files back from Françoise. Had to make a handful of typographical errors to get files to validate.
One file had no content in the English source (don't know why) so didn't have content in the translation. (Magnetic)
One file held up pending revision by Parks Canada. (ParksSummary)
Two files still in translation (Dickens1, Dickens2)
One file wasn't clear what content should go in (ErebusMusterRoll).
One instance of files now in the svnrepo/data/text/fr3xml folder. Another instance in the dev/French/FilesFromTranslateXML folder. Another in the dev/filesToProcess folder.
Also updated the filetracker.xls file.
Reviewed plan and what I've done and wrote to Nina and RS on status:
I have completed these targets:
17 Oct 2014 Set up OJS on our own server
29 Oct 2014 Review modifications approach with OJS for approval
I have partially completed this:
29 Oct 2014 Learn about relevant elements and programming requirements in OJS for required modifications
I have not completed these:
05 Nov 2014 Create new submission status data field
13 Nov 2014 Display new submission status on appropriate pages
I'm behind schedule due to a combination of unreliable documentation and my slowness at figuring out from other plug-ins the details of how to get the OJS code to do things. I don't know how long it will be before I can get a plugin to have any effect, let alone the specific effects we want.
I suggest that we assign some of Shawn's hours to work with me on this aspect of the project. RS replied that Shawn is fully committed but can informally consult when I hit a roadblock, so I emailed Shawn to ask for a few minutes on my failure to get the default plugin to behave properly.