You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is the first obvious place to begin on a tool that generates docmaps that can leverage our TS SDK. This tool should run on a command line, with parameters find some documents that are docmapsy, and generate a docmap for each of them. It should be paginated such that it can run as a long-running process and should output to stdout or a plugin. Ideally, generalize from this to a tool whose outputs and inputs are pluggable.
The text was updated successfully, but these errors were encountered:
Things I am wondering about as I work on this: in what situation does a user want to do streaming/pagination vs a single preprint/DOI?
Use cases I imagine:
docmap for one DOI
docmap for all DOIs under a prefix
docmap for every preprint that crossref can generate a docmap for
in the latter cases I expect there would be historical generation followed by fast-forward behavior when new entities come in. But do we know crossref's pagination would work that way? Best bet is to sort by creation date I suppose...
This is the first obvious place to begin on a tool that generates docmaps that can leverage our TS SDK. This tool should run on a command line, with parameters find some documents that are docmapsy, and generate a docmap for each of them. It should be paginated such that it can run as a long-running process and should output to stdout or a plugin. Ideally, generalize from this to a tool whose outputs and inputs are pluggable.
The text was updated successfully, but these errors were encountered: