Project

General

Profile

Actions

Bug #1621

open

morpho defaults to <customUnit/>, invalid eml

Added by Margaret O'Brien over 20 years ago. Updated almost 20 years ago.

Status:
New
Priority:
Normal
Assignee:
Category:
morpho - general
Target version:
Start date:
07/07/2004
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
1621

Description

When morpho encounters missing units in <attribute>, it defaults to the tags
<ratio><customUnit/>, which is not valid eml. A better default is
<measurementScale><nominal> for these fields.

Actions #1

Updated by Saurabh Garg over 20 years ago

Margaret, I am not able to find a case where attribute will have missing units.
Any already created eml2 document will have attributes with units, otherwise it
wont be valid eml2.
When creating a new eml2 document, you have to specify the unit on the
attribute description screen, otherwise the wizard wont move forward.
Was this happening when trying to read emlb6 documents?

<ratio><customUnit/> is not valid eml. It should have been
<ratio><unit><customUnit/>. <measurementScale><nominal> might be a better
default.

Actions #2

Updated by Margaret O'Brien over 20 years ago

I'm sorry, I wasnt specific enough. Yes, this was a beta6 to eml2 conversion.
But I dont have any examples handy at the moment (I fixed them all manually).
Basically, my point is that morpho is not creating valid eml by using the
<customUnit/> construct, and this seems contrary to the purpose of an eml
editor. My suggestion is that when morpho cant find any units for an attribute
that it default to the the simplest choice rather than the most complex. Editing
is still required, but at least the user gets an acceptable doc. I dont know how
many people are struggling with beta6 ->2.0; this item may have a very limited
market.

Actions #3

Updated by Saurabh Garg over 20 years ago

According to the code which does the conversion, a ratio is given when we
have /attributeDomain/numericDomain. By default, it should get
<nominal><nonNumericDomain><textDomain><definition>
I am not sure how you got <ratio>. Maybe, I am missing something in the code.
If you run into something similar, let me know. Or I can retrieve the old
version of the document from metacat. Do you know the name of the document
which caused the problem?

Actions #4

Updated by Redmine Admin over 11 years ago

Original Bugzilla ID was 1621

Actions

Also available in: Atom PDF