Following are the steps that To connect your repository to SEAD, you need to be carried out by a repository in order registered partner repository. The following steps are needed to get registered with SEAD and accept/publish collections from SEAD.:

1. Obtain access to SEAD system
2. Register the repository profile
3. Develop a client to pull and publish the collections

Obtain access to SEAD

...

system

To obtain access to SEAD system, please contact SEAD using SEAD contact form on the website and First the repository needs to contact SEAD and provide the IP addresses/subnets of the repository servers that will be accessing the SEAD services. Then the The SEAD team will add those addresses to its registry of partner repositories and grant access to the SEAD services for those IP addresses. 

Following The following endpoint will be accessible by the repository afterwards;
: https://seadva-test.d2i.indiana.edu/sead-c3pr/

...

Repositories need to create a profile in the JSONLD format which includes basic profile information and the other information JSON-LD format (http://json-ld.org/) that will be used by SEAD Matchmaker when recommending repositories for the objects. Repository profile must have an “orgidentifier”. This is the ID of your repository that will be used by SEAD.in its pairing between datasets and repositories. The profile should includes the following information:

• Repository name ID ("orgidentifier") - a required field that will serve as the repository ID in SEAD.
• Data types (“Data Mimetypes”) - types of files that the repository will accept.
• Collection depth (“Max Collection Depth”) - maximum collection depth that the repository can accept and deposit.
• Maximum dataset size (“Max Dataset Size”) – the size of individual files in the collection that the repository can accept.
• “Total Size” – Total acceptable size of the collection
• “Metadata Terms“- Minimum metadata fields that a collection should contain
• “Affiliations” - Organizations that a collection should be affiliated with
• “Rights Holder IDs Required” - Whether the collections should have a valid global identifier(ORCID, Clowder or Google ID) for the "Rights Holder" metadata.

Dandeniya Arachchige Charitha Madurangi - we need to add more guidelines for each field, e.g., is orgidentifier a string? a number? in what units should dataset size be? are other fields free text?

Following is a sample JSON-LD profile of a repository:Following is a sample JSONLD profile of a repository;

{"@context": ["http://re3data.org/",
  {
    "Max Dataset Size": "http://sead-data.net/terms/maxdatasetsize",
    "Rights Holder IDs Required": "http://sead-data.net/terms/RightsHolderIdsRequired",
    "Total Size": "tag:tupeloproject.org,2006:/2.0/files/length",
    "Max Collection Depth": "http://sead-data.net/terms/maxcollectiondepth",
    "motto": "http://bobs.asseenon.tv/terms/motto",
    "Affiliations": "http://sead-data.net/terms/affiliations",
    "Data Mimetypes": "http://purl.org/dc/elements/1.1/format",
    "Metadata Terms": "http://sead-data.net/terms/terms"
  }
],
  "Max Dataset Size": "1000",
  "@type": "repository",
  "Total Size": "10000000",
  "orgidentifier": "bob",
  "repositoryURL": "http://http://www.nationaldataservice.org/projects/labs.html",
  "Rights Holder IDs Required": true,
  "Max Collection Depth": "10",
  "motto": "Our profile is up to date, so we have to be good",
  "repositoryName": "SEAD NDS Labs Publisher (Proof-of-Concept)",
  "Affiliations": [
    "SEAD",
    "NDS Members"
  ],
  "Data Mimetypes": ["text/csv"],
  "Metadata Terms": [
    "http://purl.org/dc/terms/creator",
    "http://purl.org/dc/terms/abstract",
    "http://sead-data.net/vocab/test/doesntexist"
  ]
}

Currently SEAD Matchmaker considers the following profile information when making the recommendation;

...

Once the repository profile is created, it should be registered with SEAD by sending a POST request to the following endpoint with the JSONLD profile as the POST body.

...