Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.
Notice: In order to edit this ticket you need to be either: a Product Owner, The owner or the reporter of the ticket, or, in case of a Task not yet assigned, a team_member"

Task #9905 (closed)

Opened 11 years ago

Closed 11 years ago

Put OME-TIFF CustomAttributes/StructuredAnnotations in the original metadata hashtable

Reported by: mlinkert Owned by: mlinkert
Priority: major Milestone: OMERO-4.4.7
Component: Bio-Formats Version: n.a.
Keywords: n.a. Cc: i.munro@…, jamoore, ajpatterson, jburel
Resources: n.a. Referenced By: n.a.
References: n.a. Remaining Time: n.a.
Sprint: n.a.

Description

See the files in ome-tiff/ian/. All of the useful information is stored in ca:CustomAttributes, but that is not propagated to original metadata which means that it is not accessible from OMERO.

Change History (5)

comment:1 Changed 11 years ago by jmoore

  • Cc jmoore added

Are those blocks also converted to XmlAnnotations? Is there anything more we can do with them?

comment:2 Changed 11 years ago by mlinkert

They aren't converted to XmlAnnotations? at the moment. We may be able to do that too, but I haven't looked carefully enough at this point - there are a lot of moving parts here, especially since the files use the 2008-02 schema and so have to go through half a dozen stylesheets before Bio-Formats can even think about doing anything with the XML.

comment:3 Changed 11 years ago by mlinkert

There are two parts to this. The first issue is that the 2008-09-to-2009-09.xsl stylesheet drops all CustomAttributes?, when it should convert to StructuredAnnotations. That's unfortunately a little tricky - do we always create an XMLAnnotation? Or try to guess the type?

Once the stylesheet does CustomAttributes? -> StructuredAnnotations, the second part is to update OMEXMLServiceImpl.getOriginalMetadata(...) so that it fetchs all top-level StructuredAnnotations and puts them in the hashtable in some sort of sensible way.

comment:4 Changed 11 years ago by jmoore

  • Cc ajpatterson jburel added

I would think we would start by converting all custom attributes to a single xml annotation. We may from there add specific handling for well-known ones, but most likely storing the whole block as XML will be a) more useful/informative and b)less likely to lose any information. The flip side is that it will require more post-processing.

comment:5 Changed 11 years ago by mlinkert

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets. You may also have a look at Agilo extensions to the ticket.

1.3.13-PRO © 2008-2011 Agilo Software all rights reserved (this page was served in: 0.90868 sec.)

We're Hiring!