Skip to content

Connecting to the Harmonized Model Repository

Tobias Spears edited this page Mar 24, 2020 · 3 revisions

Software

  • If you do not already have a SVN client software, download and install it - see Subversion client software.

  • If do not already have Enterprise Architect, acquire it from SPARX (http://www.sparxsystems.com.au/). If your current copy is older than version 8, you probably should download the latest build and install it (there have been very useful user interface improvements for 8 that are helpful in editing (or dealing with) the HM). Because you need to construct files during set-up, you need an editor, the viewer will not suffice.

Setting up the local working copy

  • Note 1: This section is based on using the GUI for Tortoise SVN in Microsoft Windows. Similar steps will be applicable for other SVN Clients and operating systems.
  • Note 2: This section describes how to set up a read-only working copy.

For editing, continue to Editing the Harmonized Model after finishing this section.

####1. Create a directory for the local working copy E.g. "C:\Standards\ISOTC211". And create a subdirectory "iso" This is the directory where the local copies of the XMI files and directories from the repository will be stored and updated (and edited if you are an editor).

####2. Perform an SVN Checkout from the repository to your local "iso" directory In Windows Explorer:

Right-click on the selected directory and select "SVN Checkout..."

SVN Checkout

Write the URL to the repository in the checkout dialogue (https://inspire-twg.jrc.it/svn/iso/) and press "OK"

SVN Checkout dialogue

Tortoise will now establish the local working copy of the isotc211 model repository in your current directory. It will be called "iso" and have a special icon for ‘svn.’ A dialog with checkout status is shown, and should finally look something like this: SVN Checkout log

The directory with the local working copy should now look like this, with a main directory isotc211 and subfolders for each standard: SVN Local directory

Setting up Enterprise Architect

####1. Open EA and a EA Project This can be a new, empty project or an existing project.

####2. Set Version Control Settings Use the main menu to open a Version Control Dialog:

Project → Version Control → Version Control Settings

Set the following in the dialog:

  • Unique ID: ISOTC211
  • Type: Subversion
  • Working Copy Path: (the path to 'iso' from SVN step, i.e. C:\Standards\ISOTC211\iso)
  • Subversion Exe Path:(location of svn.exe for the client – probably like C:\Program Files\TortoiseSVN\bin\svn.exe)
  • Don't click private, your working copy is a shared model
  • Click "Save" and "Close", and wait for it to finish.

Version Control Settings

####3. Get models from SVN Go to the model browser (usually on the right) and use the context menu:

Package Control → Get Package.

The dialog will ask for the Version Control Configuration.

Select "ISOTC211" from the drop down menu.

The system will then list all XMI files in the repository.

Select isotc211\ISO TC211.xml, and "OK"

For including OGC standards and other ISO standards (e.g. ISO 639 - Language codes and ISO 3166 Language codes), perform the same process for the files "Other ISO Standards.xml" and "OGC.xml"

Get Package

4. Get latest version

There should now be a new package in the model called "ISO TC211", with empty subpackages. It is really an empty shell at this time. Empty packages

To get the latest version of all packages: Use the same context menu as before:

Package Control → Get All Latest

There is an option to load only changed models. This won't make a difference, since all of them are "new". The import should take a while and load all the sub-packages of the model; the model browser is a good indication of what is happening and how far it has gotten, since it is updated when each XMI mentioned in the isotc211 root is loaded.

At this point, all packages are locked, but you can browse. The full structure is now in place:

Repository ↔ Server ↔ Client (local XMI copy) ↔ EA (file)

Each time you begin, it is probably wise to repeat the "Get All Latest." Only the packages not currently checked-out will be refreshed.

To start editing the model, continue to Editing the Harmonized Model