Skip to content
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

Option: unpublished draft URL of research note, for initial review by participants #129

Closed
dwblair opened this issue Jul 25, 2014 · 9 comments
Labels
break-me-up break up for cleaner code separation, discrete tests, and, easier and iterative collaboration enhancement explains that the issue is to improve upon one of our existing features outreach issues involve community involvement and helping people who're stuck somewhere

Comments

@dwblair
Copy link
Member

dwblair commented Jul 25, 2014

I've had some outings in which I've taken photos of participants in a meeting, and I've written up some description of the event -- and I'd like to be able to send them a link to the research note before it has been published on publiclab.org, for them to review re: privacy concerns or material content ...

@ebarry
Copy link
Member

ebarry commented Jul 28, 2014

This is a very interesting idea. The urge to send out a draft for review
rings true to my experience working with a group. I've been getting around
this by urging and supporting participants to author their own research
notes.

@lizbarry http://twitter.com/lizbarry

@ebarry ebarry added the outreach issues involve community involvement and helping people who're stuck somewhere label Dec 15, 2014
@mathewlippincott
Copy link

I want to second this, and add I got the feedback from CSU students that not being able to save a draft in the Research Note UI was confusing. A "save as draft" that saves to dashboard and allows for multiple in-progress notes was Damarquis and Paul's suggestion.

I personally copy the text of partially finished reserach notes and save in text files, but that Markdown flexibility isn't immediately obvious.

@jywarren
Copy link
Member

jywarren commented Oct 27, 2015

I think we could do this as part of the Rich Editor project, but it depends
also on how much time we spec for that in the Dec/Jan cycle. Currently,
also, the Dashboard revision is slated first. I'll move all issues into a
set of milestones soon as well, with dates, so we can prioritize. Thanks!

@steviepubliclab
Copy link
Contributor

steviepubliclab commented Jan 23, 2018

Hi there, I'm up for bumping this up as well. I'd like to be able to "save" as to continue drafting later myself, and secondly the function of having others "edit" on the post before it goes live as well. Maybe this seems like two features?

I could also see this as being useful for the writing working group (if they have a user name), to work on drafting with groups.

@jywarren jywarren added the break-me-up break up for cleaner code separation, discrete tests, and, easier and iterative collaboration label Jan 25, 2018
@jywarren
Copy link
Member

Great -- steps I can think of for starters are:

  • making a draft status (maybe status = 3?) for nodes (not wiki pages), which makes it not visible to anyone but the author.
  • a POST parameter like draft=true to bypass most of the "create" method in the notes_controller and which adds the status = 3 when you publish
  • a button to post the form with the draft parameter set to true in the Rich Editor template
  • a modification of the with:____ coauthor tag (see this post which allows co-authors to see the post
  • an alert at the top of a draft page that offers a shareable link to the post for sending around
  • maybe a secret URL token that allows access to the post even if someone doesn't have an account?

... lots and lots of possible steps here. Stevie, any input on some of the ideas above, or want to choose a subset we could get started on?

Thanks!

@steviepubliclab
Copy link
Contributor

steviepubliclab commented Feb 7, 2018 via email

@grvsachdeva
Copy link
Member

Hi @jywarren @steviepubliclab Can I work on this?

@steviepubliclab
Copy link
Contributor

steviepubliclab commented Feb 7, 2018 via email

@grvsachdeva
Copy link
Member

Opened in #2304

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
break-me-up break up for cleaner code separation, discrete tests, and, easier and iterative collaboration enhancement explains that the issue is to improve upon one of our existing features outreach issues involve community involvement and helping people who're stuck somewhere
Projects
None yet
Development

No branches or pull requests

6 participants