MME Requirements, Setup Steps and Version Changes

These instructions are to set up the Minnesota Metadata Editor (MME) which allows users to view and edit metadata (documentation) using the Minnesota Geographic Metadata Guidelines (MGMG).

  • MME runs as a standalone executable program although it requires a Windows .NET framework
  • MME is packaged for distribution as a portable application 

Requirements

  • Microsoft .NET Framework 3.5
    • In order to run MME, Microsoft .NET Framework 3.5 must be installed on your machine.
    • Determine if the .NET Framework is on your machine by going to Start->Control Panel->Add or Remove Programs.
    • You should see Microsoft .NET Framework 3.5 listed.
    • Multiple versions of Microsoft .Net Framework (e.g., 1,2,3) may exist on your machine simultaneously.
    • Microsoft's .NET Framework 3.5 is freely available and can be accessed from Microsoft's website.
  • Microsoft Access Database (if editing)
    • The application itself does not require Microsoft Access installed on the local computer in order to run, although the application is data-driven using an Access database, metadata.mdb.
    • Access is required, however, in order to edit the database, for example, if you need to edit the database to assign default values that apply to your particular agency or group.
    • Once edited, the program can be distributed to other machines that do not have Access installed.

Setup Steps

  • Download and unzip the download file. Open the MME-master folder. All necessary files are in the Minnesota Metadata Editor folder. You may place the folder anywhere you wish.
  • To run the program, double-click on the MetadataEditor.exe file, found in the Minnesota Metadata Editor folder.
  • The application uses \portable\metadata.mdb as its source database. This database can be shared among several users if needed.

Additional Notes

  • You shouldn't need special administrative privileges to set up the program.
  • The application needs no installation and uses one copy of the application database for anyone who runs the application. Nothing is installed or modified on the machine running the program. All files are kept in the folder containing the application.
  • Running the application from a network drive can cause problems so we don't recommend it.

Post-Installation Steps

MME can be installed and run in several modes:
  • As an installed application on your computer
  • As a portable application

MME normally installs as a normal Windows .NET program. When installed, a local copy of the application database is created from the program's \template directory on first run for each user. The user's copy of the application database can be further customized as needed per individual by selecting Tools > Open Database. Admin privileges are required for this installation.

Run as portable application, MME needs no installation. Further, rather than making a copy of the template application database for each user, it uses just one copy of the application's database for everyone who runs it. Nothing is added or modified on the machine running the program. All files are kept in the folder containing the application. If the application is stored on the local computer or a USB drive, you can launch Access to edit the application database using Tools > Open Database. You may store the folder with the application on a network drive and run it directly from there. However, the help file will not display correctly nor can you use Access to directly edit a database on a networked drive due to security issues.

Whether MME is installed on your computer or run portably, it can be helpful to take preliminary steps to customize key settings to meet your needs. Here's an overview of post-installation steps.

Using the Editor as an Installed Application

If you are using the editor as an installed application, then go to the Windows Start > Minnesota Metadata Editor to open it.

An installed version of the MME always uses a local copy of the application database stored in the user's data directory.

The first time an installed application is started, the user's local directory is checked for a copy of the database. If none is found, a new folder is added to the user's Documents local data directory and a copy of the contents the application's \template folder is made. The \template folder contains the metadata.mdb.
..\Minnesota Metadata Editor 1.1\template   >>>> ..AppData\Roaming\MnGeo\Minnesota Metadata Editor\.

Using the Editor as a Portable Application

If you are using the editor as a portable application, then go to its location and double-click Minnesota Metadata Editor.exe to run it.

If the application finds a \portable folder in its directory, it uses \portable\metadata.mdb as its source database. This database can be shared among several users if needed.

If no \portable folder is found, the application makes a copy of the \template\metadata.mdb into the user's local directory that can be personalized for the individual user.

Setting Up the MME Database

When you first install MME or set it up as a shared portable application, it can be helpful to edit the MME Database to ensure that the defaults for the metadata fields match your specifications. Please see the help section titled 'Customizing the Metadata Editor Database' for more information on configuring the database with default values to meet your needs.

Changes in Version 1.2

  1. Forced "mailing and physical" in addrtype fields for contacts on these tags since it is a required field for the federal data.gov website:
    - idinfo/ptcontac/cntinfo/cntaddr/addrtype
    - distinfo/distrib/cntinfo/cntaddr/addrtype
    - metainfo/metc/cntinfo/cntaddr/addrtype
  2. XSL template MGMG.xsl
    - restored the 'HTTP' protocol to hyperlinks
    - allowed HTTPS as a URL protocol for hyperlinks
  3. Removed all references to MnGeo in program setup folder.
  4. Changed the Spatial Extent of Data field to a text box (from a combo with pull-down list).
  5. Fixed Online Linkage field, so that the publisher text is not erased when doing a refresh from database.
  6. Changed default text in Online Linkage to be more generic since not all data is available for download:  "I AGREE to the notice in "Distribution Liability" above. Clicking to agree will either begin the download process, link to a service, or provide more instructions. See "Ordering Instructions" above for details."
  7. All help now links directly to a website at MnGeo.
  8. Minnesota County Coordinate System now supports "feet" as well as "meters" for NAD83 datum.
  9. Extraneous blank rows in database tables removed. This should prevent people from setting blank values as default.
  10. Added check for database version and fail to load if the wrong database is used - link user to a help page.
  11. Added fields: Vertical Datum, Vertical Units, Depth Datum, Depth Units, Browse Graphic Description.
  12. Modified fields Publication Date, Progress of Data, and Update Frequency to pull-down lists + text entry.
  13. Removed the address2 field in the database table for Contact_Information since it is not a supported element in the Minnesota Geographic Metadata Guidelines.

Upgrading from a Prior Version

This version of MME makes several changes to database structures and is not backward-compatible with earlier database formats. During start-up the application checks to determine if the database is in the correct format and will not proceed with an earlier version.
Install the new version in a new location and then edit the new database as needed to provide the default values for your configuration. Look in the MME help for more detailed instructions on user-configurable values in MME and how to set them.