8000 Integrating patterns and coding memos · Issue #100 · Hypertopic/Cassandre · GitHub
[go: up one dir, main page]
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.

Sign up for GitHub

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

Jump to bottom

Integrating patterns and coding memos #100

Open
christophe-lejeune opened this issue Jan 14, 2020 · 0 comments
Open

Integrating patterns and coding memos #100

christophe-lejeune opened this issue Jan 14, 2020 · 0 comments
Labels
Feature Refactoring

Comments

@christophe-lejeune
Copy link
Member

During my last stay in Troyes, @benel suggested to merge patterns and coding memos. The name of selected coding memos could be used as a search key (pattern) to produce KWICs. This elegant idea would bring back former qTopics (semi-automatic codes in Cassandre 1.0).

Such a feature should be easy to implement and might even simplify the software. A checkbox may allow the user to use a coding memo name as a pattern.

Where KWICs will be featured is still under question.

  • Consisting of previews from field memos, KWICs may find their place among groundings of the coding memo. However, in desktop design, groundings appears in a left panel, that is too narrow to fit the KWICs. Groundings panel would better work for mobile designs (where groundings appears above memo content)... but I am unsure it would be easily understood. Moreover, locating KWICs among groundings suggest that the automatic link should be treated as other groundings. This would lead to additional development (that will be done if this option is retained).
  • KWICs may also find their place in a dedicate panel, under the content of the memo. This behavior introduces a new zone in the interface (thus renders the software more complicated for the user). It however allows another feature in regards to the relation between KWICs and groundings : each line of the KWICs could be provided with an anchor icon, allowing the user to decide which field memo deserves to be used as grounding for the coding memo. Such a feature would be less automatic (and less impressive) but it might better fit the epistemology of the software.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Feature Refactoring
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@christophe-lejeune
0