asset.meta.validate isn't case-sensitive in its testing?

[John Twyman]

Hi folks,

I have a metadata definition that has an enumerated element that defines "yes" and "no" values. I have an asset with this definition against it where the current value for that element is "No".

If I modify the asset in the Hydrogen desktop, the interface clearly marks the element as being invalid. However, when I run:

asset.meta.validate :id <id>

it seems to think the asset is perfectly valid. My only guess here is that asset.meta.validate isn't case-sensitive in its assessment. Is that the case?

I'm running mflux 3.9.002, desktop 1.0.77 and aterm 2.6.

Cheers,

John

[Jason Lohrey]

We will modify the desktop to (as it should) perform case-insensitive validation for enumeration types that are, by default, case-insensitive.

--
You received this message because you are subscribed to the Google Groups "mediaflux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mediaflux+...@googlegroups.com.
To post to this group, send email to medi...@googlegroups.com.
Visit this group at http://groups.google.com/group/mediaflux.
For more options, visit https://groups.google.com/d/optout.

JASON LOHREY

Chief Technical Officer

[Evan Thomas]

Hi John,

your hypothesis is correct, the server is doing a case insensitive comparison while the desktop compare is doing a case sensitive comparison. This is not correct - we will change desktop so that by default the comparison is case insensitive. We will provide an option in the document definition GUI to specify whether enumerations should be case sensitive (which you will be able to apply retrospectively to existing definitions).

Evan.

Evan Thomas

Senior Software Engineer

ARCITECTA

5/26-36 High Street, Northcote

Victoria, Australia 3070

T:+61 3 8683 8527

M:+61 423 000 246

F:+61 3 9005 2876

http://www.arcitecta.com

Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer does not consent to email or messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of Arcitecta shall be understood as neither given nor endorsed by it.

On 30 Apr 2014, at 9:57 am, John Twyman <john....@sydney.edu.au> wrote:

[Evan Thomas]

I tried to reproduce but wasn’t able to. Would you mind sending me the doc definition and asset metadata (off the group list if you prefer)?

asset.doc.type.script.create :type doc-ns:doc-name :out file:/some/path/doc.tcl

asset.query :where id=<id> :action get-meta :out file:/some/path/asset.xml

Evan.

Evan Thomas

Senior Software Engineer

ARCITECTA

5/26-36 High Street, Northcote

Victoria, Australia 3070

T:+61 3 8683 8527

M:+61 423 000 246

F:+61 3 9005 2876

http://www.arcitecta.com

Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer does not consent to email or messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of Arcitecta shall be understood as neither given nor endorsed by it.

On 30 Apr 2014, at 9:57 am, John Twyman <john....@sydney.edu.au> wrote: