-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation request: Annotator use case #33
Comments
Thanks for the feedback, glad you like the annotator! In short, you should use the Annotator to transform records that are stored locally in your R session, and use "Dataset Migrations" to transform datasets that are already on SolveBio. In the end, it is up to you how you want to process the data. In many cases you can do a bunch of annotations in one step, but you can use intermediate datasets for transforms that require more than one step (such as merging/comparing datasets). I'll together some examples for you and also add them to the developer docs. |
Thanks! Can you add an example of how to follow the progress of a migration? It doesn't seem to appear in the activity tab until it is complete and present in the activity tab of the current UI |
Good point, this will be fixed in the new version of the site. For now, you can use some R code to follow along: migration = DatasetMigration.create(...)
while(migration$status == "queued" || migration$status == "running") {
migration <- DatasetMigration.retrieve(migration$id)
cat(migration$status, sep="\n")
Sys.sleep(3)
} |
Thanks! If you have similar snippets for the specific questions I listed, that would be much appreciated. |
Hi,
Annotator function is awesome! I would like to use it to annotate an ad hoc dataset that has a primary id via a shiny app.
Can you provide some R examples of how to
(ideally limited to a specific vault, and a count of id appearances from list in each dataset)
(it isn't clear if I should annotate all at once or create intermediate datasets that I delete)
Thanks
Iain
The text was updated successfully, but these errors were encountered: