Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Integrating eagle-i resources into Profiles application:

  1. SWEET application is required
    1. Profiles URIs need to be added to all Person records in eagle-i
  2. Define the base URL for Profiles
    1. In the, add a new property eaglei.datatools.profilesBase
    2. The expected value of this property is a URL
    3. The default value of this property is
  3. Create a csv file that maps the name of the resource type as defined by the eagle-i ontology and the desired display name
    1. The expected name of the file is profiles-resource-label-mappings.csv
    2. The expected location of the file is in the same directory as the file, in other words, the eagle-i config directory.
    3. The expected format of the file is:
      1. lines that start with '#' and blank lines are ignored
      2. each line is one mapping
      3. each mapping is in the form of key,value. These are case sensitive.

      4. keys starting with * indicate a partial match and are meant to cover several eagle-i terms that share a common part. For example, *Mus means that both Mus and Mus Musculus will be mapped.
    4. Sample file: profiles-resource-label-mappings.csv
    5. For the mapping *Mus,Mouse strains:
  4. Set up an external process which accesses the eagle-i profiles web service and writes the response to a location. This process should be recurring to get updated information.
    1. The web service is located at [your eagle-i installation]/sweet/profiles.
    2. For example, Harvard's eagle-i profiles web service is located at
  5. Configure Profiles application to access this resource dump (following Profiles instructions)
  • No labels