Integration with Profiles

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 eagle-i-apps.properties, 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 http://connects.catalyst.harvard.edu/profiles/profile/person/
3. In order to display resource types in a user friendly and compact format, a csv file is required. 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 eagle-i-apps.properties 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 http://harvard.eagle-I.net/sweet/profiles
5. Configure Profiles application to access this resource dump (following Profiles instructions)