NOTE: The Evaluation services were initially introduced as the Competition services
Table of Contents |
---|
Overview
...
Synapse Evaluations are constructed around three primary objects: Evaluation , Participant, and Submission. These objects are defined by eponymous JSON schema files in the Synapse Repository Services. The UMLet file used to generate the following image is available here.
Evaluation
Object representing a Synapse Evaluation
- ID - unique ID for the Evaluation
- eTag - optimistic concurrency flag; changes with each update
- ownerID - principal ID of the owner of the Evaluation
- name
- description
- contentSource - ID of the data source (e.g. entity) for the Evaluation (string)
status - enum describing the state of the Evaluation, one of: PLANNED, OPEN, CLOSED, COMPLETED
...
- ownerID - principal ID of the Participant
- evaluationID
- createdOn - join date
Submission
Immutable object to represent an entity submission to a Evaluation. A participant can create many Submissions for a given Evaluation.
- ID - unique ID for the Submission
- name
- ownerID - principal ID of the Submission owner
- evaluationID
- entityID - ID of the submitted entity
- version - specific entity version
- createdOn - submission date
- submitterAlias - the alias for the user or team creating the submission
SubmissionStatus
Object to track the status and score of a specific Submission. This object is generated at the time of submission, and can be modified by Evaluation administrators.
- submissionID
- eTag - optimistic concurrency flag; changes with each update
- status - enum describing the state of the Submission, one of: OPEN, CLOSED, SCORED, INVALID
- score - numerical score for this Submission (double between 0 and 1)
- report - String describing this Submission and/or its scoring. May contain additional scoring information, error logs, etc.
- annotations - Annotations object containing user-defined key-value annotations. Note: The contents of the annotations are mirrored to a second set of tables optimized for querying, as discussed here.
SubmissionBundle
Bundle object containing a Submission and its accompanying SubmissionStatus.
SubmissionStatusBatch
Used to upload a collection of Submission updates at once.
REST API
Evaluation
URL | HTTP Type | Description |
---|---|---|
/evaluation | POST | Create a new Evaluation |
/evaluation/{evaluationId} | GET | Get a Evaluation |
/evaluation/{evaluationId} | PUT | Update a Evaluation |
/evaluation/{evaluationId} | DELETE | Delete a Evaluation |
/evaluation | GET | Batch Get Evaluations (Paginated) |
/evaluation/count | GET | Get the number of Evaluations |
/evaluation/name/{name} | GET | Find a Evaluation by name Note that the name must be URL-encoded |
Participant
URL | HTTP TypeDescription | |||
---|---|---|---|---|
/evaluation/ | {evaluationId}/participantPOST | Join as a Participant in a Evaluation * | ||
/evaluation/{evaluationId}/participant/{principalId} | POST | Add another user as a Participant in a Evaluation. * Requires admin rights on the Evaluation. | ||
/evaluation/{evaluationId}/participant/{principalId} | GET | Get a Participant | ||
/evaluation/{evaluationId}/participant/{principalId} | DELETE | Delete a Participant | ||
/evaluation/{evaluationId}/participant/ | GET | Batch get Participants for a given Evaluation(Paginated)available | GET | Get the paginated list of Evaluations which the user has joined as a participant. |
/evaluation/{evaluationId}/participant/count | GET | Get the number of Participants in a given Evaluation |
...
, status (OPEN,CLOSED,...) |
Submission
URL | HTTP Type | Description |
---|---|---|
/evaluation/submission?etag=<etag> | POST | Create a new Submission (and corresponding SubmissionStatus object). Required request parameter: |
/evaluation/submission/{submissionId} | GET | Get a Submission |
/evaluation/submission/{submissionId}/status | GET | Get the status of a Submission |
/evaluation/submission/{submissionId}/status | PUT | Update the status of a Submission. |
/evaluation/submission/{submissionId} | DELETE | Delete a Submission. Requires admin rights on the Evaluation. |
/evaluation/{evaluationId}/submission/ /evaluation/{evaluationId}/submission/bundle/ | GET | Batch get my Submissions/SubmissionBundles for a given Evaluation. Optional request parameters: |
/evaluation/{evaluationId}/submission/all /evaluation/{evaluationId}/submission/status/all /evaluation/{evaluationId}/submission/bundle/all | GET | Batch get Submissions/SubmissionStatuses/SubmissionBundles for a given Evaluation. Optional request parameters: |
/evaluation/submission/{submissionId}/file/{fileHandleId} | GET | Get a temporary pre-signed URL to a File contained within a specified Submission. Optional request parameter: |
/evaluation/{evaluationId}/submission/count | GET | Get the number of Submissions for a given Evaluation. |
Access Restrictions
Access Restrictions and approvals may be applied to Evaluations. For details on the API see: Data Access Control
cURL Examples
Evaluation
Create an Evaluation
Code Block curl -i -k -H sessionToken:xxxxxxxxxxxxxxxx -H Accept:application/json -H Content-Type:application/json -d '{ "status":"PLANNED", "description":"description", "name":"my first evaluation", "contentSource":"contentSource" }' https://repo-staging.prod.sagebase.org/repo/v1/evaluation
Get an Evaluation
Code Block curl -i -k -H sessionToken:xxxxxxxxxxxxxxxx -H Accept:application/json 'https://repo-staging.prod.sagebase.org/repo/v1/evaluation/1588317'
Update an Evaluation
Code Block curl -i -k -H sessionToken:xxxxxxxxxxxxxxxx -H Accept:application/json -H Content-Type:application/json -X PUT -d '{ "id":"1588317", "createdOn":"2013-01-16T16:30:56.727Z", "etag":"eed22bca-d88e-4b4a-8b1a-35dca7b7b8db", "status":"OPEN", "description":"description", "ownerId":"1588313", "name":"my first evaluation", "contentSource":"contentSource" }' https://repo-staging.prod.sagebase.org/repo/v1/evaluation/1588317
Delete an Evaluation
Code Block curl -i -k -H sessionToken:okxkSRyl3v0iIf0eutQfXA00 -H Accept:application/json -X DELETE 'https://repo-staging.prod.sagebase.org/repo/v1/evaluation/1588317'
Participant
Create a Participant
Code Block curl -i -k -H sessionToken:xxxxxxxxxxxxxxxx -H Accept:application/json -H Content-Type:application/json -d '{ "ownerId":"123456" }' https://repo-staging.prod.sagebase.org/repo/v1/evaluation/987654/participant
...
Delete a Participant
Code Block curl -i -k -H sessionToken:xxxxxxxxxxxxxxxx -H Accept:application/json -X DELETE 'https://repo-staging.prod.sagebase.org/repo/v1/evaluation/1588317/participant/1588313'
Submission
Create a Submission
Code Block curl -i -k -H sessionToken:xxxxxxxxxxxxxxxx -H Accept:application/json -H Content-Type:application/json -d '{ "evaluationId":"1588317", "entityId":"1588315", "versionNumber":"1", "name":"some-name" }' https://repo-staging.prod.sagebase.org/repo/v1/evaluation/submission
Update a SubmissionStatus
Code Block curl -i -k -H sessionToken:xxxxxxxxxxxxxxxx -H Accept:application/json -H Content-Type:application/json -X PUT -d '{ "id":"1589914", "modifiedOn":"2013-01-18T21:43:18.897Z", "etag":"13c88b1a-662c-4dd6-bb56-3976566516f7", "status":"SCORED", "score":0.42 }' https://repo-staging.prod.sagebase.org/repo/v1/evaluation/submission/1589914/status
Delete a Submission
Code Block curl -i -k -H sessionToken:dPF2TqGUq121PR36AwJhXw00 -H Accept:application/json -X DELETE 'https://repo-staging.prod.sagebase.org/repo/v1/evaluation/submission/1589912'
...
- Banned user lists
Banned users should be prohibited from participating in one or more Evaluations, and any Submissions by a banned user should be isolated from the general populations of Submissions.Jira Legacy server JIRA (sagebionetworks.jira.com) serverId ba6fb084-9827-3160-8067-8ac7470f78b2 key PLFM-1646 - Customizable Amazon Simple Notification Services messaging tools
Evaluation administrators should have tools to configure a selective Amazon instance to listen for messages pertaining to Evaluations which they own. These messages should be sent to a queue dedicated to Evaluations.Jira Legacy server JIRA (sagebionetworks.jira.com) serverId ba6fb084-9827-3160-8067-8ac7470f78b2 key PLFM-1647 - Immutable copies of submitted Entities
Once an Entity is submitted to a Evaluation, a static copy of that Entity should become the property of the Evaluation administration.Jira Legacy server JIRA (sagebionetworks.jira.com) serverId ba6fb084-9827-3160-8067-8ac7470f78b2 key PLFM-1648 - pAdministrator Administrator lists for Evaluations
Evaluations should support administration by multiple users (rather than just the Evaluation owner). These admin lists should function as a lightweight ACL of sorts.Jira Legacy server JIRA (sagebionetworks.jira.com) serverId ba6fb084-9827-3160-8067-8ac7470f78b2 key PLFM-1649