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

Add "save as" functionality #10

Open
derekdreery opened this issue Jun 29, 2020 · 1 comment
Open

Add "save as" functionality #10

derekdreery opened this issue Jun 29, 2020 · 1 comment

Comments

@derekdreery
Copy link

I created a term set then accidentally started from that codeset when creating another. Now if I save the new term set I will overwrite the previous one. If I could save the new term set as a new record I could get round the problem.

@rw251
Copy link
Owner

rw251 commented Jul 7, 2020

I agree. This is actually 2 things. First is making it harder for people to accidentally work on an existing set (but i think that will probably get covered by #14), and second is adding the "save as".

The "save as" (which should be the focus of this ticket) would be most useful for the use case where you've created a codeset which you want to use as a starting point for a new one - which I guess is exactly what "save as" is for.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants