-
-iGEM parts should be compliant (dispalyID)
-iGEM parts have annotation to iGEM entry url
-have support for collections
-have support for filtering by type
-
For example, have collections for similar groups of data (iGEM, BO, etc). Also, change java API so I can search only parts in a specific collection and get all the parts from a specific collection. …
-
Clicking on Download SBOL, gives:
Cannot GET /component/igem/BBa_K136042/BBa_K136042/1.xml
-
Clicking on Download FASTA, gives:
Cannot GET /component/igem/BBa_K136042/BBa_K136042/1.fasta
-
For options below I would expect URI compliance and completeness not to be checked (i.e., adding the -n and -i flags). This does not seem to be the case:
json: { 'options': {'language' : 'SBO…
-
A lot of the data has URIs with information on displayId, but the actual displayId field is empty. Would it be possible to ensure best practices/compliance on the data?
-
The next button does not work with advanced search. Need someway to remember the query when pressing next/previous.
-
We are getting segmentation fault errors when reading a SBOL2 file and then writing the read in file. The seg fault is happening on the write.
A simple C++ program was created that takes in a file…
-
If an SBOL Document contains elements not in a recognized SBOL or extension namespace, those elements should be passed through serialization
-
If a part is imported from SBOLStack/is iGEM part, add clickable link to a wasDerivedFrom field in the part editor.