Home

myequivalents1 is a system to manage cross-references between entities that can be identified by pairs composed of a service name (e.g., EBI's ArrayExpress, Wikipedia) and an accession (e.g., E-MEXP-2514, Barack_Obama). For those familiar with the Semantic Web, we plan to support identification of entities via URIs and the owl:sameAs property. For those who already know MIRIAM and identifiers.org, myequivalents is more general than them and we plan to support these services in future.

Please, see this presentation before reading this guide.

##Current Status With respect to the slides mentioned above, at the moment the software has these limitations:

• only a basic service is implemented, only mappings that are explicitly stored can be fetched back, there is no code that implements closure over service collections. Nor is the MIRIAM support available yet.
• the web service implements only methods to access existing mappings. Storing new mappings or service-related information can only be done via command line or programmatically and only if one has access to the relational database that backs the myequivalents service (see below for a description of the different component types available). The idea is that, for the time being, mapping storage is something restricted to a single organization or to a few people, while accessing existing mappings is someone that can be made accessible to a wider user base. For instance, this is a typical scenario if your organisation has to maintain a cross-reference service.

## Where to go from here

• Architecture
• Building the Software
• Programmatic Access
• The Command Line Access
• The Web Service
• The Web Service Client