Clarify difference between saving in "Local" and "Concordance Registry"

[stefandesu]

It should be made very clear that mappings saved in "Local" are only available inside the browser that is currently used, i.e. they are not available for anyone else AND they get lost if the user resets or changes their browser. I would suggest clarifying this both in the manual and in the user interface.

Also, we could think about setting the standard registry to "Concordance Registry" even if the user hasn't logged in yet. When trying to save, we could show a message that either the user can log in to save to the public Concordance Registry, or switch to "Local" with the clarifications mentioned above.

[nichtich]

I think most use cases don't require a local storage anyway. Maybe remove it from the master instance and keep in dev only?

[stefandesu]

Local Storage is a good way to get people to try Cocoda without having to create an account. I do agree that removing local storage completely would be easiest, but this might also lead to people trying it out and saving test mappings into our mapping registry.

My suggestion would be: When the user saves a mapping into local storage for the first time, show a modal popover which clarifies the caveats of using local storage and explains how the user can create an account and use the main mapping registry. What do you think?

[nichtich]

Yes, giving a warning with link to documentation is better

[stefandesu]

I opted to show a normal alert with an explanation and a link to the manual. Please adjust the text if necessary, @nichtich.