Difference between revisions of "Steps to EOL integration"

From mx Help Wiki
Jump to: navigation, search
(New page: ==Overview== Based on conversation with C. Parr Mar. 3/10 EOL transfer documentation is here: http://services.eol.org/schema/EOL_Transfer_Schema_Documentation.pdf, with a glossary...)
 
Line 1: Line 1:
 
  
 
==Overview==
 
==Overview==
Line 8: Line 7:
  
 
Mx content types should map to the Species Profile Model [[http://rs.tdwg.org/ontology/voc/SPMInfoItems.rdf]]
 
Mx content types should map to the Species Profile Model [[http://rs.tdwg.org/ontology/voc/SPMInfoItems.rdf]]
 +
 +
Preparing EOL files: http://hickory.eol.org:8081/display/dev/Preparing+EOL+Schema+Files (includes XML validation)
  
 
* no specimens
 
* no specimens
 
* images are linked to taxa, captions should clearly denote
 
* images are linked to taxa, captions should clearly denote
 
* image and object metadata take care of the attribution and licensing of the objects
 
* image and object metadata take care of the attribution and licensing of the objects
 
  
 
== To do (mx) ==
 
== To do (mx) ==

Revision as of 14:32, 3 March 2010

Overview

Based on conversation with C. Parr Mar. 3/10

EOL transfer documentation is here: [[1]], with a glossary here: http://eol.org/files/pdfs/docs/EOL_Transfer_Schema_Glossary.pdf

Mx content types should map to the Species Profile Model [[2]]

Preparing EOL files: http://hickory.eol.org:8081/display/dev/Preparing+EOL+Schema+Files (includes XML validation)

  • no specimens
  • images are linked to taxa, captions should clearly denote
  • image and object metadata take care of the attribution and licensing of the objects

To do (mx)

  • settle on routing for services API /api/eol?
  • write Template#eol returning an XML object as per the "mushroom" example
  • have EOL hit /eol, get a list of available pages, then crawl the other URIs
  • consider formalizing or providing the SPM "content_types" as defaults
Personal tools