Skip to topic | Skip to bottom
Metadoor.DeveloperNotesr1.10 - 05 Oct 2006 - 14:33 - JeremyCothrantopic end

Start of topic | Skip to actions


Update October 5, 2006 The development group at Arizona Hyrdologic Information System (AHIS) has installed a Meta-Door system and provided the following helpful installation notes .

If you do setup an independent Meta-Door installation, we'd appreciate if you could give credit (maybe a link back to the Meta-Door twiki homepage ) somewhere on your website and a notice by email to jcothran[at] so that we can help coordinate possible updates or funding needs.

The below are some comments by the developer Bashar who works with AHIS:

Comment begin

We made quite a few changes to metadoor, and now itís fully integrated with AHIS (You can check it here: . You need to create yourself an account first and then click on Manage my metadata). Thanks to use of Tiles changing the layout and content was pretty easy!

I didnít write any more documentation after the last document I sent. Building and running Metadoor can be a bit tricky; I really suggest using Maven instead of ant to better manage Metadoor.

One issue I didnít like about metadoor is the use of postgre dump tool to generate SQL scripts. It generates a lot of postgre-specific code that works only with Postgre which locks you into only using postgre database with metadoor. Another issue I didnít like is mapping xml elements to relational tables. This is really a complicated process that is very hard to scale and maintain. I would have preferred keeping the xml elements in their native binary format (in xml files) and read/write to the xml files directly. This would greatly simplify the design of the database and makes adding support to more elements a whole lot easier.

Other than that the source code was pretty clean and easy to understand. Thanks for sharing such a good project.

Comment end

Sourceforge File Download

Update April 27, 2006: The available source code which has been provided at sourceforge and elsewhere is a very old version - contact jcothran[at] if you are looking for the most recent files.

A download of a zipped package of source code files is available at

Sourceforge CVS

An online viewable sourceforge CVS for Meta-Door is located at

Notes on Sourceforge CVS usage can be found at

Note that for sourceforge commands, the project name is 'osioss' the module name is 'meta-door2' and the user name will either be the developer name or 'anonymous'.

Command Line

#for all cvs steps set the CVS_RSH environment variable
export CVS_RSH=ssh

#if prompted for anonymous password, press enter
cvs login

#to download entire meta-door module
cvs -z3 co -P meta-door2


WinCVS settings for download and updates. For developers, substitute the developer name for 'anonymous'

Installation notes

Note: In the process of moving production boxes, the materials currently available don't quite cover what's completely needed. I'm in the process of adding and documenting these remaining elements.

Support Code Versions

C:\Program Files\Java\jre1.5.0_04

Struts 1.2.4
Apache 2.0

General Info

The paths listed for the downloaded files would live under the tomcat webapps directory similar to


Environment arguments which will be specific to your environment are located in the following files and should be changed accordingly


The application assumes that mp (metadata parser install package at has been installed under the default option of C:\USGS

And the files currently used to configure and run mp at


assume the CATALINA_HOME environment variable is defined as C:\jakarta-tomcat-5.5.5 and should be checked and changed as needed to match the environment setup

Run 'ant all' from webapps\meta-door2 initially and after any change to the database tables.

Source files

Contact jcothran[at]

For a PostgreSQL? GUI database interface we use and I'd recommend EMS detailed more at the following link

Coordinating development efforts

The initial application has been developed using Java/Struts/Hibernate running against a PostgreSQL? relational database(although the SQL code should be non-database specific).

For developers who wish to suggest fixes or added features that work within the above framework, the following is suggested:

  • notify jcothran[at] of the development ideas in case something is already in the works
  • make and test your changes locally
  • submit changes to jcothran[at] for testing and incorporation into the sourceforge cvs

For further development, the underlying table schemas could also be used for development towards other non-Java specific interfaces(php,etc) or a variety of xml schema exports.

For developers wishing to branch outside of this framework(say using the same database, but supplying command line exports or interfaces using perl, php, python, etc), the same above steps would apply, but a different sub-version of Meta-Door may end up being created supporting specific functionalities.

Batch processing

Used the following perl script and mp config file to clean up xml files so they are passed through mp successfully generating all the other format outputs.

-- JeremyCothran - 24 Aug 2005
to top

I Attachment Action Size Date Who Comment
wincvs_1.bmp manage 441.0 K 24 Aug 2005 - 16:56 JeremyCothran NA
wincvs_2.bmp manage 441.0 K 24 Aug 2005 - 16:56 JeremyCothran NA manage 2.2 K 27 Feb 2006 - 17:54 JeremyCothran NA
meta-door-publish.cfg manage 0.2 K 27 Feb 2006 - 17:55 JeremyCothran NA manage 13971.3 K 11 May 2006 - 23:24 JeremyCothran NA manage 23.8 K 11 May 2006 - 23:24 JeremyCothran NA manage 2863.4 K 11 May 2006 - 23:24 JeremyCothran NA
SETUP.html manage 11.1 K 05 Oct 2006 - 13:26 JeremyCothran NA

You are here: Metadoor > DeveloperNotes

to top

Copyright © 1999-2018 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Carocoops? Send feedback