Mikado

[Devrim Tezcan]

You can download Mikado java tool and user manual from

http://www.seadatanet.org/Standards-Software/Software/MIKADO

The latest version (version 7) of java should be installed in your computer ( http://www.java.com/en/download/manual.jsp)

To run the mikado, double click on mikado.bat in Windows OS, run the command ./mikado.csh in Linux or MacOS

[Devrim Tezcan]

Federica added a bathymetric metadata example under the topic “Metadata tools”, and I add here a CTD example. Open and check please these different metadata examples in Mikado:

• ·      Manual Menu > Open > File > CDI
  
• ·      Browse the xml file
  

Please check the entries and compare with your data.

[Alina Spinu]

[catia.chiappini]

Another CDI CTD Example

[Federica Foglini]

Here an example of multi beam bathymetry for the Adriatic Sea

[Federica Foglini]

Hi Alina,

I am not able to oper your xml file, I got an error, can you check it and send it again to us

[Alina Spinu]

Hi Federica,

I am not longer at work but I checked again and I can open the file direct from googlegroup - it is an example of CSR (cruise summer report)

[Federica Foglini]

Thanks Alina, I will try to open it as CSR

[catia.chiappini]

I think that Mikado is a really good tool to make cdi but for my little experience (only with ctd data) a little bit intricate if you need to manage/create a lot of cdi (expecially if you have a lot of stations as usually is in xbt/ctd cruises).
I think that the goal is to find a way to automate the process and once generated a cdi model, proceed  with a script to create an xml file for every profile getting different values from an input file.
For my experience I've used Nemo software (downloadable from SeaDataNet site at this url http://www.seadatanet.org/Standards-Software/Software/NEMO) to create a "cdi summary" file (cvs format) and then imported in Mikado to generate all the xml cdi files for my cruise (all my ctd stations).

[Vivi Drakopoulou]

 An easy way to produce cdi with Mikado is pre prepaired an excel template which can fill all the mandatory fields of cdi.  As soon as possible I will try to create this file for biologic data for Coconet project. Today I will sent you a excel for Bathymetric data.

[Francesca Lisi]

Hi Everyone,

During this workshop Valentina and me, we used Mikado for the first time, and despite being quite easy to deal with it, we have some question to ask.

 

Cruise/station tab: which is the difference between these two information fields?  Provisionally we filled both field with the same name.

Others tab: which data format and what version should we adopt? Does it depend on data type? For example we are filling a .xml file for each shape file (sample points, cruise lines, DTM bathymetry).

Please find attached three .xml example files we work on, based on three layers we had: first one about points (sample points), second about polylines (cruise lines) and third one about a surface (DTM bathymetry).

 

Thanks

Francesca

[Vivi Drakopoulou]

I would like to make a comment here about the metadata descriptions and the available tools to generate this descriptions.

CDI (generated by Mikado) is used for data (eg. field observations like scientific cruises, multibeam surveys etc) description, discovery and access.
Geonetwork tool is used for data products (eg. DTM, model outputs, shape files thematic layers etc) description, discovery and access.

So our HCMR and our NODC team approach based on our experience as partners in SeaDataNet, EMODNET Chemical, bathymetry Pilots, etc is to use the both above tools for project needs.

At the links below you can find some examples of chemical and bathymetric DTM products 
EMODNET chemistry: http://www.ifremer.fr/sextant/en/web/emodnet_chemistry/catalogue
EMODNET hydrography: http://www.ifremer.fr/sextant/en/web/emodnet_hydrography_cprd/catalogue

Furthermore I'll send you some xml through Geonetwork tool we have created during MESMA project.

[Devrim Tezcan]

You can validate the xml schema in

http://www.seadatanet.org/validator/

Devrim

[francescodeleo]

Hi Devrim
I've tried to run the validation procedure(http://www.seadatanet.org/validator/) for the various .xml files that we have shared in these days, but for many of them the process failed (errors and hazards have been reported). why does it happen?
Francesco

[Anna Sebova]

Dear Francesco,

I can explain that this error appears because your xml file refers to another standard.

It is seen from your file name and tags... 
SeaDataNet use ISO19115.

Regards,
Anna

[alessandro.sarretta]

Dear all,
I have a general question on the MIKADO software. I see that it is widely used in the SeaDataNet community, and it is developed by IFREMER.
Do any of you know whether its source code is available anywhere and, if the answer is not, why it isn't developed as an open source software?
I see a lot of good opportunities in opening this piece of software, because of possible integration with other tools, improvements by other communities, maybe specific plugins to interact with INSPIRE-related tools and services...
I don't know much about the SeaDataNet community, so maybe this has been discussed a long time ago and several times ...
Thanks
Ale

[Aurore Chassanite]

Dear all,

 

After trying three times to install mikado, the software is still not working on my personal computer. Apparently I have a problem with java. So unfortunatly I will not be able to tell you what I think of this software before the end of this workshop. But I will see our computer expert at work tomorrow and try to install it on an other computer. I really want to try it anyway.

Devrim and Frederica I will let you know later if it works for genetic data.

 

Sincerely

Aurore

[Devrim Tezcan]

From Peter Thijsse...

Dear Alessandro, Devrim,

 

Devrim forwarded me you question.

 

MIKADO plays a crucial role in the SeaDataNet I and currently SeaDataNet II project for generation of metadata of marine datasets, research projects etc. It produces formats which are used internally in SDN by all connected partners, and make use of many vocabularies of fixed terms to describe parameters, organisations, platforms etc.

The code of Mikado is indeed developed by IFREMER during. As far as I know the source is not available (yet) but it is for sure not developed as OpenSource. The reason is that it gets its added value by being very closely related to all developed interfaces in the SDN project and the standards used must be applied very well otherwise the supplied formats have no use.

This does not mean however that the software, as well as the used vocabularies, is not expanded for additional marine data domains/communities e.g. driven by Emodnet pilot projects and the SDN II project. It is well adapted for marine geochemical data, physical data, and currently being upgraded e.g. for marine biological data types.

Specific upgrades are also on the way to make the exported formats ISO19139 compliant.

 

There is a lot more to say what is going on, but I hope the above already gives you an idea of the widespread use to the software.

 

Peter Thijsse

MARIS (Technical Coordinator SeaDataNet)