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

Save != publish #130

Open
nuest opened this issue Mar 25, 2020 · 10 comments
Open

Save != publish #130

nuest opened this issue Mar 25, 2020 · 10 comments
Assignees
Projects

Comments

@nuest
Copy link
Member

nuest commented Mar 25, 2020

When creating a new ERC, the "Save" button is actually a publish button. It would be helpful, especially for public links for review (#118) and to avoid authors making their ERCs public unintentionally, if "Save" only updates the metadata, and an extra "Publish" button _with a "are you sure" warning for making the ERC publicly available.

I think we had it that way in the old UI, right?

The "are you sure"-dialog could also point out that you can get in touch with the o2r team to get a publicly shareable link.

@MarkusKonk
Copy link

No, we never had that. We only distinguished between candidates and and non-candicates (which get the status automatically after updating the metadata). Distinction between unpublished ERCs (non-candidates) and published ERCs (also non-candidates) has not been considered somewhere so far, not even in the metadata. But we could just add a field from the UI-side.

@nuest
Copy link
Member Author

nuest commented Mar 25, 2020

For me, a candidate is an unpublished compendium, so sorry for not being clear.

There are no "unpublished ERCs", just "candidates", "candidates with a public link", and "published ERCs".

@MarkusKonk
Copy link

The point is that candidate at the moment is either true or false, no "true with public link" so far. I will just change the metadata.

@MarkusKonk
Copy link

But: As I rememver, one of your services changes the candidate state automatically from true to false after updating the metadata, if I remember that correctly.

@nuest
Copy link
Member Author

nuest commented Mar 27, 2020

You are correct! https://o2r.info/api/compendium/candidate/

I suggest:

  • I update the API to enable metadata updates without publishing
    • The client will have to set candidate: false
  • The "Save" button is still renamed to "Publish", because that is what it does, and we add again the "Are you sure" question; the window for this question can also tell the author, that to delete a compendium, she has to reach out to the o2r team (and give our email)
  • When the API is updated, we can add an extra "Save metadata" button

@MarkusKonk
Copy link

Agreed

@nuest
Copy link
Member Author

nuest commented Apr 1, 2020

@MarkusKonk Can you go ahead with the button renaming and adding of the "are you sure" question?

@MarkusKonk
Copy link

Is the API update done?

@nuest
Copy link
Member Author

nuest commented Apr 1, 2020

No, but at the moment "Save" effectively is "Publish" and can be renamed. Then, when the API exists (I don't want to rush that right now) we can add the additional "Save" button.

@MarkusKonk MarkusKonk added this to Backlog in UI via automation Apr 9, 2020
@njakuschona njakuschona moved this from Backlog to Necessary in UI Sep 18, 2020
@nuest
Copy link
Member Author

nuest commented Sep 18, 2020

  1. API spec > Add option to save without publish, add action for publishing api#85
  2. API implementation > https://github.com/o2r-project/o2r-muncher/issues
  3. UI implementation (this issue)

@nuest nuest assigned njakuschona and unassigned MarkusKonk Sep 23, 2020
@nuest nuest moved this from Next to Sprint in UI Sep 23, 2020
@nuest nuest moved this from Sprint to Next in UI Sep 23, 2020
@nuest nuest moved this from Next to Sprint in UI Nov 27, 2020
@nuest nuest self-assigned this Nov 27, 2020
@nuest nuest moved this from Sprint until next release to Next in UI Dec 4, 2020
@nuest nuest moved this from Next to Sprint until next release in UI Apr 30, 2021
@nuest nuest moved this from Sprint until next release to Next in UI Apr 30, 2021
@nuest nuest moved this from Next to Next next in UI May 14, 2021
@nuest nuest moved this from Next next to Next in UI May 28, 2021
@nuest nuest moved this from Next to Sprint until next release in UI May 28, 2021
@nuest nuest moved this from Sprint until next release to Next in UI Jul 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
UI
  
Next
Development

No branches or pull requests

3 participants