In the legacy webapp it has been already implemented. Look here
for an example.
(gene:FBgn0030596 is the LUI)
You can use the new WS /service/entity-representation/ which recevies in input lui and format. For now only rdf format is implemented
alpha.flymine.org/alpha/service/entity-representation?lui=gene:FBgn0004053&format=rdf
If the lui is wrong a 404 status code is returned
curl "http://localhost:8080/biotestmine/service/entity-representation?lui=gene:MAL3P3.6test&format=rdf" { "executionTime":"2021.06.17 13:15::42","wasSuccessful":false,"error":"The lui doesn't exist","statusCode":404}
In the legacy webapp it has been already implemented. Look here for an example. (gene:FBgn0030596 is the LUI) You can use the new WS /service/entity-representation/ which recevies in input lui and format. For now only rdf format is implemented alpha.flymine.org/alpha/service/entity-representation?lui=gene:FBgn0004053&format=rdf If the lui is wrong a 404 status code is returned
curl "http://localhost:8080/biotestmine/service/entity-representation?lui=gene:MAL3P3.6test&format=rdf" { "executionTime":"2021.06.17 13:15::42","wasSuccessful":false,"error":"The lui doesn't exist","statusCode":404}