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

Preventing duplicate memos #83

Open
christophe-lejeune opened this issue Apr 12, 2019 · 1 comment
Open

Preventing duplicate memos #83

christophe-lejeune opened this issue Apr 12, 2019 · 1 comment

Comments

@christophe-lejeune
Copy link
Member

When the user creates a memo, the software should check that the proposed name does not exist yet. If it is the case, the creation should be interrupted and the user prompted that a memo with the requested name already exists.

Such a feature is preferable to a drop down menu suggesting an existing name when the user is typing the name of the memo to be created. Indeed, proposing to create a link with an existing memo may suggest that repetition is not a problem (or, even, may be interpreted as a encouragement to re-use existing memos rather than creating a new one). The design of the UI should of course discourage such (wrong) interpretations.

christophe-lejeune added a commit that referenced this issue Jun 4, 2019
When the user creates a memo, the page checks whether the proposed name exists in the diary. If it is the case, the creation is interrupted and the user prompted that a memo with the requested name already exists.

This commit also includes the following feature :
* Prompting the user when username and password do not match.
@christophe-lejeune
Copy link
Member Author

This feature could be improved by checking for existing memos before the user hits the create button. This could be done by the same mechanism that autocomplete uses.

Maybe the dialog prompt could provide a button allowing to grounds the current memo in the existing memo. Such a feature would require to check that the type of the existing memo matches the type of memo that the user is attempting to create.

christophe-lejeune added a commit that referenced this issue Nov 11, 2019
Refactored rewriting rules 5249d4f broke the user-filtered view of diaries. Fixing this rewriting rule restores the feature preventing duplicate memo names (#83).
christophe-lejeune added a commit that referenced this issue Dec 6, 2019
Up to now, if the user tried to create a memo with a name that already existed in the diary, he was prompted (though a dialog box) that a memo with that name already exists.

From now on, the platform suggests to ground the existing memo in the current one (through a one-click operation). The user is simply prompted (with no suggestion) if the grounding link already exists.
christophe-lejeune added a commit that referenced this issue Jul 25, 2022
When the user fills the add/create input field, a list of existing memos is suggested (as #83 proposed), allowing to add the current memo among the groundings of the selected memo.

If the user requests an already existing grounding, s/he is prompted that it already exists. If the memo is already grounded, but on a different fragment/paragraph, the grounding is quietly updated.

This feature can contribute to smoother coding sessions, as @benel indicates (#112). That's why it is reserved to field memos and transcripts at this stage.
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

1 participant