fixed the level 1 representation for the get endpoint

[waterflow80]

fixes #48
The refactor was straightforward, because we coded the seqcol level attributes in a separate class: JSONLevelOne, and it is separated from the meta-data, like the naming_convention, and digest.

The output of the GET (retrieval) endpoint with level=1 is now:

{
    "sequences": "dda3Kzi1Wkm2A8I99WietU1R8J4PL-D6",
    "names": "mfxUkK3J5y7BGVW7hJWcJ3erxuaMX6xm",
    "lengths": "Ms_ixPgQMJaM54dVntLWeovXSO7ljvZh",
    "md5-sequences": "_6iaYtcWw4TZaowlL7_64Wu9mbHpDUw4",
    "sorted-name-length-pairs": "Yz3kB58sQCEWKRbx9KOW5x6Gc7OJlgIs"
}

Note: we fixed the hyphen convention-underscore convention in another PR.

Suggestion

We can add another endpoint that gives the user the possibility to fetch the seqcol object with other metadata.

So the new endpoint may be like:

• ../collection/{digest}/metadata
• or ../collection/{digest}/extended
• or ../collection/{digest}?level=1&moreInfo=1

A discussion must be done to choose the best endpoint schema

[tcezard]

Looks good to me.
As stated in the meeting, sequence collection is meant to be able to contain any metadata we want so we should add the naming convention and source assembly directly in the collection.