Example usage:
Pass URL of a file to -
http://dts1.browndog.illinois.edu/extract/
Return JSON -
{
"MediciExtractorID1": "foo",
"MediciExtractorID2": "bar",
"VersusExtractorID1": "32040940328400238409328409832"
"VersusExtractorID2": "038409324723987429837498273493984723947"
"ExtractorID1": "http://dts1..." (a preview/previews)
"ExtractorID2": "http://dts1..." (a preview/previews)
}
As we have begun to integrate Versus into Medici this can be setup within Medici by adding the desired interface. Also, as this is a service for potentially lots of data we want to avoid storing all files passed to Medici within Medici. We just want the extractors to run on them, return the result, and throw the file away. We may need an option implemented within Medici to allow this.
- FF-depends on
-
MMDB-1425 Track which extractor created a particular piece of metadata
- Resolved
-
MMDB-1443 API endpoint to add tags to datasets/files/sections
- Closed
-
MMDB-1444 Store extractor_id for machine generated tags
- Closed
-
MMDB-1418 Track extractor status (i.e. starting, completed)
- Resolved
-
MMDB-1451 Store extractor_id for previews
- Resolved
-
MMDB-1419 Add support for files indexed on other sites
- Closed
-
BD-59 Setup VM: dts1.ncsa.illinois.edu
- Done
-
BD-61 Create a quick extractor for face detection using OpenCV
- Done
-
BD-28 DTS REST interface
- Done
- relates to
-
BD-142 Have DTS push status information into local mongo instance
- Done