New Feature Addition · Manuscripts · Created by
J B Dorman
closed
Auto-release Manuscript Series
What functionality is missing? What is unsatisfying with the current situation?
The ability for a manuscript to become public once a pre-defined time has been reached.
How does this feature request address the current situation?
Setting a manuscript to switch from private to public at a defined time allows the owner to set a release date for the manuscript upon it's completion without needing to return to the manuscript later. This will be particularly useful for any manuscript with an announced release date, such as E-books or ongoing series. Users with access to the manuscript feature currently are required to go back to the manuscript at the date and time they wish to publish the work to manually set it from private to public, which can wreak havoc on your schedule as it prevents the user from uploading at the expected time if their connection is lost or if they are indisposed for any reason.
What are other uses for this feature request?
This feature could be expanded for even greater functionality by implementing a form of 'multi-release' sub-feature. This hypothetical feature could allow the manuscripts writer to set multiple release dates, each of which either allowing a specified group of subscribers to view it or make it public. However even if the feature as a whole is accepted I would not expect this addition to be added to it, as I would assume it is far more difficult.
For example, the writer sets the first release date to one week from now, and allow the 'test reader' subscriber group to view it. Next, they set a release date two weeks from now, and allow the 'patreon supporter' group to view it. Second to last they set a third release date six days after the patreon supporter release that allows the 'friends group' subscriber group to view it before making a final release date a total of three weeks after completion to make the manuscript public and visible to all users.
Final Notes
If you choose to downvote this because you believe it to be impossible or too difficult to implement (or simply feel strongly that this feature would be to the detriment of the community) and have the time, I would be extremely grateful if you added a message explaining why. I understand next to nothing about code and have only participated with the community a small amount, so if making this request is a mistake a good response explaining why the idea is flawed might help myself and others to understand the website better and avoid making the same mistake in the future.
The Team's Response
This suggestion has not reached the required votes or community participation during its voting period.
This is not a bad feature suggestion, or a bad idea at all but due to the fact that
this will require the introduction of a new time-checking features across the board
had very little support
I cannot accept it today. Please feel free to resubmit at a later time.
Current score
46/300 Votes · +6660 points