{"id":206,"date":"2011-10-12T08:20:37","date_gmt":"2011-10-12T08:20:37","guid":{"rendered":"http:\/\/blogs.sussex.ac.uk\/salda\/?p=206"},"modified":"2011-10-12T08:20:37","modified_gmt":"2011-10-12T08:20:37","slug":"the-magic-restructuring-the-ead-to-rdf-xslt-transform","status":"publish","type":"post","link":"https:\/\/blogs.sussex.ac.uk\/salda\/2011\/10\/12\/the-magic-restructuring-the-ead-to-rdf-xslt-transform\/","title":{"rendered":"“The Magic” – restructuring the EAD to RDF XSLT transform"},"content":{"rendered":"

By Pete Johnston<\/strong><\/p>\n

In a previous post<\/a> I described how I had used an XSLT transform to generate RDF\/XML from the EAD XML representation of the Mass Observation Archive catalogue exported from the CALM archival data management system. My approach was to take the XSLT I’d created within the LOCAH project<\/a> to process the Archives Hub EAD data as a starting point, and to amend and extend it to processs the MOA data.<\/p>\n

In that post, I suggested that there were some aspects of the transformation process which were more “general” and based on structural conventions that were common to, maybe not all, but a large subset of EAD documents, while others were more specific\/”local” to the particular content of the MOA data, and that it might be possible\/useful to try to separate out these different parts of the processing to make it easier to apply only the general\/generic processing and to “swap in” different “local” processing as required for different input datasets.<\/p>\n

While thinking about this, I broke things down further:<\/p>\n