Skip to content

Specify Forums

Personal tools
You are here: Home » Discuss Specify! » Specify Forum » Query about DiGIR "enhancement"

 • Query about DiGIR "enhancement"

Document Actions
Replies: 1   Views: 4713
Up one level
You need to be a registered member to post to this forum.

 • Query about DiGIR "enhancement"

Posted by mcwinans at 2007-07-23 06:01 PM
The list of enhancements for version 5.2 states that "Sites can now place Microsoft Access files containing query and text file Darwin Core mappings in the directory containing Specify.exe. Specify looks for these files in its directory, and if it finds them, skips the previously required download step and imports the local files." However, I have been unable to discover any documentation of this new feature. Where can I find information about how to make this work?

 • Re: Query about DiGIR "enhancement"

Posted by kcoggins at 2007-07-24 01:20 PM

There is a missing chunk from the documentation below the line...

What should be added that if the DiGIR query does NOT get downloaded from our website after we have said it is available, we can get the query to you with some other means (mail, email, etc) and you can place it in the Specify exe directory and Specify will check that location for the query.

If you want these instructions in a word doc, please email us and we will send it to you in that version.

Generating a DiGIR Data Set
The installation procedure described in the preceding section gives you the software to run DiGIR with Specify, but it doesn’t prepare the Specify data for the DiGIR system. DiGIR does not access the Specify database directly. Instead, it uses a special, read-only database generated from the Specify data. Once you’ve installed DiGIR, you’ll need to initiate the process of creating and exporting a read-only DiGIR copy of your Specify database. This page shows you how to do that.
Important: You must install DiGIR before you can generate the DiGIR data.
The data contents of the DiGIR data set depend upon the data fields that are active when the export occurs. For this reason, you should complete the task of customizing your Specify data forms before you choose the export command in step 1 below. Contact the Specify Software Project if you don’t know what this means.
Before You Begin: The DiGIR data set export process described below may take several hours of processing time. Do not start this until you are able to allocate your workstation for several hours for this activity.
To generate the DiGIR database:
1. From the Specify menu bar, choose Tools > Admin> DiGIR Settings > Export DiGIR Metadata. This command assembles a package of information on your Specify program and uploads it to a server that can be accessed by the Specify staff.
2. Contact the Specify Project by email at and request a custom DiGIR search. Be sure to mention the name of the institution and the type of collection (e.g., bird, mammal, or fish).

The Specify Project builds the search and sends it to the server described in step 1. The team will inform you when the custom search is ready.
3. After you have saved the custom search on your computer, choose Tools > Admin> DiGIR Settings > Import DiGIR Search.

You are ready to generate the DiGIR data.
4. Choose Tools > Admin> DiGIR Settings > Update DiGIR Data to generate the DiGIR data. This command runs the DiGIR search you imported and populates the DiGIR database. It also automatically updates the DiGIR configuration files to include information on your local DiGIR implementation. The Update procedure may take several hours for a large database, so you may need to let the update run overnight.
Filling Out the Metadata Form
The first time you select Export DiGIR Metadata, Specify asks for some information through the DiGIR metadata form. It displays a series of fields in the left column and lets you enter values for the fields in the right column. The fields are:

Field Name Description
abstract A description of your DIGIR provider site.
citation How to cite information retrieved from the DiGIR provider.
keywords Keywords associated with the DiGIR provider site. For example: vertebrates, photographs, field notebooks, correspondence.
maxInventory ResponseRecords The maximum number of records that can be returned in an inventory (scan) response.
maxSearch ResponseRecords The maximum number of records that can be returned in a search response.
minQueryTermLength The minimum number of characters that can appear in a query term.
name The common name of the resource. For example: The Hildebrand Collection.
recordBasis The type of records available. For example, voucher or observation.
recordIdentifier An identifying code that can be recognized in the records of the resource.
recordLimit The recordLimit parameter is not used at this time. Leave this setting blank.
relatedInformation Location of information about the DiGIR provider. Should be full URL. For example:
useRestrictions Any restrictions regarding the use of information retrieved from the resource.

After you enter values for these settings, Specify will apply them to subsequent exports. You will not be prompted to enter these settings the next time you export DiGIR metadata. If you wish to view or modify any of these parameters, choose Tools > Admin> DiGIR Settings > Edit DiGIR Settings.
Ideally, you might only need to export, import, and update the DiGIR data once to get your system working. Practically speaking, the DiGIR search and the DiGIR database may require some adjustments. Be prepared for more than one iteration of the DiGIR update process described in the preceding section.
How Often Do You Need to Update?
Because the DiGIR database is separate from the Specify database, later changes to the Specify collection will not be automatically reflected in DiGIR. You'll need to rerun the Update DiGIR data command to incorporate changes to the Specify database into DiGIR.
If you have only added additional records to the collection database and haven’t made any changes to the Specify fields or forms, you do not need to export the DiGIR metadata or import a new query. Simply update the DiGIR data by choosing Tools > Admin> DiGIR Settings > Update DiGIR Data.
The frequency for DiGIR updates depends on how often you add new records to your Specify collection. Large and active collections will need to run the DiGIR update nightly. Less active collections can update the DiGIR database once per week.
How Often Do You Need to Export Metadata?
If you make a change to a Specify field that is used in the DiGIR database, you’ll need to initiate the full process for importing a new DiGIR query and regenerating the DiGIR data. Repeat the steps under "To generate the DiGIR Database" above.

Viewing DiGIR Data and DiGIR Security
A user can restrict the data that is available through their DiGIR Provider.

To Restrict the Search or Viewing of a Particular Field:
• You must edit these field settings from a configuration file located under the DiGIR directory under program files.
• The file you must locate is an XML file in this directory.
You can either of the following:
• Delete the line for the filed being careful not to leave any tangling XML lines.
• Set the searchable and or viewable to zero for the particular field where the default value is 1.
To Restrict Viewing from Specify
• Within the Specify form customizer a user can set the security of specify fields to certain levels of security for viewing. Any field that is set to a "Group Permitted to View" above the level of guest will automatically be blocked out by DiGIR in the making of the DiGIR cache.

Posts: 7


Powered by Plone

This site conforms to the following standards: