Bug #1833

morpho should support eml-2.0.1

Added by Matt Jones over 14 years ago. Updated over 13 years ago.

morpho - general
Target version:
Start date:
Due date:
% Done:


Estimated time:


Morpho 1.5.1 produces eml-2.0.0 documents. It also only searches for eml-2.0.0
documents and prior. We need to make it easy for morpho to support new versions
of eml, especially versions that are backwards compatible with earlier eml
versions. This might involve creating a jar download of the EML schemas and
stylesheets and a config file telling morpho how to handle crucial aspects of
the eml (maybe not needed). If this jar file can be downloaded by morpho then
we could upgrade existing morpho installations without the user having to get a
new version of the software. At a minimum we need a new release of Morpho that
creates and searches both EML2.0.0 and EML 2.0.1 documents.


#1 Updated by Saurabh Garg over 13 years ago

This bug is almost fixed. Things that had to be done to fix this bug:

1. Morpho creates eml-2.0.1 documents
2. Tree editor is able to handle both eml-2.0.1 and eml-2.0.0 documents
3. Data package wizard screens could be accessed from documentation menu for
both eml-2.0.1 and eml-2.0.0 documents. hence dpw should be able to handle both
eml-2.0.0 and eml-2.0.1
4. Similarly, Data import Wizard should also be accessed from the menu. In
addition, this wizard will be called for eml-2.0.0 documents when someone tries
to import data into an eml-2.0.0 document. Hence it should be able to handle
both the schemas.

1 and 2 are done.
3 is not a problem yet because I havnt seen any field being used in datapackage
wizard which is different for eml-2.0.0 and eml-2.0.1 documents.

4 is what is left to do. Specifically, dateTimeDomain is optional in one schema
and not optional in another. Hence that should be handled accordingly in data
import wizard screens. This problem is mentioned in bug# 2162 with a little
more description. Hence fix for this bug will fix that bug too.

#2 Updated by P. Anderson over 13 years ago

This was waiting on the eml-2.0.1 prompt bug which is now closed.

#3 Updated by Redmine Admin about 6 years ago

Original Bugzilla ID was 1833

Also available in: Atom PDF