17/08/17

Permalink 08:49:10 am, by mholmes, 33 words, 3 views   English (CA)
Categories: Activity log; Mins. worked: 45

Protocol doc for Maple Ridge geomapping

AC has produced an excellent protocol doc for the mapping, which I've read through and commented. I'm beginning to understand the process a bit better, but there are still gaps in my knowledge...

05/07/17

Permalink 04:17:53 pm, by sarneil, 117 words, 7 views   English (CA)
Categories: Activity log; Mins. worked: 150

map NNM DB fields to RAD ATOM fields

Spent couple of hours with KJ working out how to map fields from the NNM csv output to fields conformant with the RAD standard for input to AtoM. More or less completed the collection, series and file levels, started on the item level.
To be researched further:
- external links to jpgs (vs uploading into db as digital objects
- create authority record for Mr. Sato and figure out how to link to it.
- check RAD spec for any constraints on e.g. identifier values, or syntactic requirements

csv import documentation for AtoM 2.1 at https://www.accesstomemory.org/en/docs/2.1/user-manual/data-templates/rad-template/#template-description

RAD specification at http://www.cdncouncilarchives.ca/RAD/RAD_Chapter01_July2008.pdf

23/06/17

Permalink 02:55:53 pm, by mholmes, 92 words, 13 views   English (CA)
Categories: Activity log; Mins. worked: 240

Meeting and decisions; paper draft 3 done

Met with JSR and RRR to discuss the geo-reffing of the Maple Ridge plans. Decisions are in my notes; the basic idea is to use the identifiers from the land titles db properties table for the GIS polygons. I started examining how well our data fits with the key plans, and it's not a perfect fit at all. More work to be done here.

Finished draft three of the JAEH article, with additional material on multi-ethnicity in Japan suggested by JSR based on something in EO's paper. That's now back with JSR.

21/06/17

Permalink 04:32:59 pm, by mholmes, 29 words, 10 views   English (CA)
Categories: Activity log; Mins. worked: 120

Work on mapping of obsolete/obscure kanji

Yesterday and today, working with SA on his TEI abstract; we now have a more sophisticated approach to the obsolete kanji and their modern equivalents, encapsulated in the ODD.

19/06/17

Permalink 12:50:34 pm, by mholmes, 26 words, 17 views   English (CA)
Categories: Activity log; Mins. worked: 40

XQuery to generate list of ja owners

At AK's request, wrote some XQuery to extract a list of Japanese owners who were the last owners of a property prior to the dispossession date.

Permalink 12:49:44 pm, by mholmes, 20 words, 17 views   English (CA)
Categories: Activity log; Mins. worked: 40

Created new copy db for Powell St

Per request from AG, created a new test db copied from Powell St but basically empty, for error-checking duplicate insertions.

01/06/17

Permalink 09:08:13 am, by mholmes, 267 words, 11 views   English (CA)
Categories: Activity log; Mins. worked: 60

Extinguished properties added to Vancouver db

After a lengthy discussion and agreement, I've added the same "extinguished properties" feature to the Vancouver db as exists in the Maple Ridge db. SQL:

DROP TABLE IF EXISTS `titles_to_ext_properties`;
CREATE TABLE IF NOT EXISTS `titles_to_ext_properties` (
  `tte_tte_id` int(11) NOT NULL auto_increment,
  `tte_prop_id_fk` int(11) NOT NULL,
  `tte_title_id_fk` int(11) NOT NULL,
  PRIMARY KEY  (`tte_tte_id`),
  KEY `tte_prop_id_fk` (`tte_prop_id_fk`,`tte_title_id_fk`),
  KEY `tte_title_id_fk` (`tte_title_id_fk`)
) ENGINE=InnoDB  DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci AUTO_INCREMENT=1 ;

ALTER TABLE `titles_to_ext_properties`
  ADD CONSTRAINT `titles_to_ext_properties_ibfk_1` FOREIGN KEY (`tte_prop_id_fk`) REFERENCES `props` (`prp_property_id`) ON DELETE CASCADE ON UPDATE CASCADE,
  ADD CONSTRAINT `titles_to_ext_properties_ibfk_2` FOREIGN KEY (`tte_title_id_fk`) REFERENCES `titles` (`ttl_title_id`) ON DELETE CASCADE ON UPDATE CASCADE;

Additions to local_classes.php:

//In title class, before preceding titles field:
$this->addField(new MdhOneToManyField('ttl_ext_properties', 'Extinguished properties',
                                'ttl_title_id', 
                                'props',
                                'prp_property_id',
                                'prp_desc',
                                'titles_to_ext_properties',
                                'tte_tte_id',
                                'tte_title_id_fk',
                                'tte_prop_id_fk',
                                true, 'prp_desc', true));
//In properties class, before related properties field:
$this->addField(new MdhOneToManyField('own_extinguishing_titles', 'Extinguished by titles',
                                'prp_property_id', 
                                'titles',
                                'ttl_title_id',
                                'ttl_desc',
                                'titles_to_ext_properties',
                                'tte_tte_id',
                                'tte_prop_id_fk',
                                'tte_title_id_fk',
                                true, 'ttl_desc', true));

Tested in dev, rolled out to live, awaiting any anomaly reports from the RAs in the field.

26/05/17

Permalink 03:35:54 pm, by mholmes, 65 words, 15 views   English (CA)
Categories: Activity log; Mins. worked: 60

Extinguishing titles

Long and confusing email discussion about the difficulties in entering data about titles extinguishing properties, especially when moving backwards through title records; you end up having to re-edit a later title you've already entered when you discover from an earlier title that it actually extinguished some lots. I don't see a good technical solution to this as yet, but something may emerge from the discussions.

25/05/17

Permalink 05:02:46 pm, by mholmes, 17 words, 12 views   English (CA)
Categories: Activity log; Mins. worked: 200

Finished second draft of article

Responded to all JSR's comments, added some additional sections, and reformatted to fit the journal submission guidelines.

24/05/17

Permalink 09:01:18 am, by mholmes, 59 words, 11 views   English (CA)
Categories: Activity log; Mins. worked: 60

Maple Ridge DB: new field and updated triggers

Per AG's request, added a new Range field to the property table, reconfigured the triggers to take account of it, and then updated all the desc fields (since we also made a small change in April). Code used is in the repo as trigger_update_2017-05.txt; tested on dev then run on live. Backups taken before and after.

:: Next Page >>

Landscapes of Injustice

Reports

XML Feeds