-
Notifications
You must be signed in to change notification settings - Fork 21
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
Update figshare screen recording metadata #207
Comments
Yes, smart.
I got the notification and already moved it to the Manubot project before I saw this. However, now it is marked private. I'm not sure if this is a project-level setting or not.
Okay...
Sounds good. |
Made project public at https://figshare.com/projects/Manubot/62288 |
@slochower I don't see a way to edit https://figshare.com/account/projects/62288/articles/7946192. Perhaps you need to add me as an author? Sometimes the figshare interface leaves a bit to be desired! |
The journal resubmission instructions include
I was not planning to upload this video because it is already available on figshare. Is that our intention, or should I also upload it as a video? The journal might make a second copy on figshare in that case. |
One benefit of including it is that it could show up in the Figshare element at the bottom of the page (example): Ideally, PLOS could include a figshare item in the "Supporting Information" section without having to re-upload it. Not sure if this is possible. The ideal situation:
However, I'd rather have 1 without 2 than neither. |
I still don't see how to edit, so I created a ticket (ticket link will only work for me): |
I found an example manuscript with supporting videos: https://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1006068#sec013 They do play in the figshare widget. I expect that we would have to re-upload the video to get that, which is acceptable. However, their instructions request videos of at most 10 MB. I'll see what options we have to submit as is, but the submission system may not accept it. |
I can perhaps fiddle with the export resolution until it is that small, but my fear (without actually checking) is that bumping the resolution that far down will make the webpage text in the video unreadable. At which point, it may be better to make a new version. |
Let's keep the current resolution for the resubmission. I agree that we need reasonable resolution to keep the text readable, and I'll explain that if they push back. |
Radu Gheorghiu, an Integrations Engineer at Figshare, responded to my help ticket and wrote:
I didn't realize there was no way for multiple figshare accounts to edit the same item. Too bad. Therefore, I can just leave what updates I think we should make in a comment here that @slochower can apply to the record. Feel free @slochower to remove me as an author, since that didn't accomplish what we were hoping. |
@slochower how about the following? Feel free to change a bit. Also you should be able to show us unpublished version by link before finalizing. Title: "How to edit a manuscript on GitHub with Manubot" Description: The screen recording shows how to edit a manuscript via GitHub using Manubot. Manubot is the the manuscript bot for automated scholarly publishing. It is an open source software project for writing scholarly documents using GitHub. Learn more at https://manubot.org. This screen recording is used as a supporting data video for the manuscript describing Manubot at https://greenelab.github.io/meta-review/. This latest version of this Figshare item is available at https://doi.org/10.6084/m9.figshare.7946192 or shortened to https://doi.org/c4fz. Add a PNG high-rez screenshot as second file like (but same dimensions as video): This will be used as the clip to show before video is played. Probably want to rename files to
In case we ever want to add more videos to this record. |
Note: The link https://doi.org/10.6084/m9.figshare.7946192 goes to the original movie, before I moved it to the Manubot project. However, if I go to "Cite" on the Manubot project version, it gives me the same DOI. I clearly am having difficulty with the FigShare UI. Is this because the version in the Manubot project is still marked private?
|
The DOI link will direct to the latest published version. The private
version is not published yet.
Regarding rename, you must delete file and upload with changed name.
…On Thu, Apr 11, 2019, 3:01 PM David Slochower ***@***.***> wrote:
- ✓ Updated Title
- ✓ Updated Description
Note: The link https://doi.org/10.6084/m9.figshare.7946192 goes to the
original movie, before I moved it to the Manubot project. However, if I go
to "Cite" on the Manubot project version, it gives me the *same* DOI. I
clearly am having difficulty with the FigShare UI. Is this because the
version in the Manubot project is still marked private?
[image: image]
<https://user-images.githubusercontent.com/5393995/55984110-90071380-5c51-11e9-807e-4255d42df59d.png>
- ✓ Uploaded PNG for title (the so the object is now a "file set").
I'm not sure whether this will affect autoplaying or not.
- ✗There appears to be no way to actually change the movie filename as
uploaded. It is not an editable field.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#207 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABEOB6HT57hKyNbwSlxxJpsod8RHntLPks5vf4akgaJpZM4cn5Xz>
.
|
Won't either of these things (re-publishing or re-uploading) give a new DOI? Just making sure we propagate the changes... |
Re-uploading in the same item should not automatically publish. Isn't there
a publish button? I believe the publish button should create a v2 rather
than a new record
…On Thu, Apr 11, 2019, 3:13 PM David Slochower ***@***.***> wrote:
Won't either of these things (re-publishing or re-uploading) give a new
DOI? Just making sure we propagate the changes...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#207 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABEOB0DU5zNb0gOy--I7_8Jua1YqrHbyks5vf4lXgaJpZM4cn5Xz>
.
|
I think the private version should now have the files correctly named. |
Okay the private version now looks good to me. One small change: can you reorder the files to make the video come first? This will make it possible to directly watch the video from the landing page. I think the upload page supports drag and drop reordering. No worries if this doesn't seem possible. @slochower proceed with v2 publication. |
Should be good. |
But I think maybe you have to make it public. |
Great published at https://doi.org/10.6084/m9.figshare.7946192.v2
I don't think so, but let me know if otherwise. |
Well, I see it is public now, but even after I clicked Publish, it still said Private, and I couldn't find any way to change that. Could be ineptitude on my part. Anyhow, nice work. |
See #213 to remove the DOI to version 1. The unversioned DOI should point to the latest version, which is probably what we want. |
This build is based on 3b83c5e. This commit was created by the following Travis CI build and job: https://travis-ci.org/greenelab/meta-review/builds/518964155 https://travis-ci.org/greenelab/meta-review/jobs/518964156 [ci skip] The full commit message that triggered this build is copied below: Update figshare URL to v2 suffix Merges #213 Refs #207
This build is based on 3b83c5e. This commit was created by the following Travis CI build and job: https://travis-ci.org/greenelab/meta-review/builds/518964155 https://travis-ci.org/greenelab/meta-review/jobs/518964156 [ci skip] The full commit message that triggered this build is copied below: Update figshare URL to v2 suffix Merges #213 Refs #207
@slochower created a screen recording to address #139, which we added to the manuscript in #191. Version 1 is at https://doi.org/10.6084/m9.figshare.7946192.v1
I'd like to do the following:
@slochower move current deposit to the Manubot Figshare Project. You can do this by checking the box under my data and using the Actions dropdown.
I will propose some more complete metadata including a different title and changed metadata.
I will add a snapshot, such that the video embed can default to showing the video title rather than a black screen.
The text was updated successfully, but these errors were encountered: