Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Better indicate occurrences #271

Closed
nichtich opened this issue Feb 13, 2019 · 4 comments
Closed

Better indicate occurrences #271

nichtich opened this issue Feb 13, 2019 · 4 comments
Labels
low priority maybe later user experience Usage should be fun and easy
Milestone

Comments

@nichtich
Copy link
Member

Occurrences of a given concept should better be shown distinct from co-occurrences by adding a straight line or em-dash in the column of the second concept scheme so its more clear that only one concept scheme is references.

@nichtich nichtich added the user experience Usage should be fun and easy label Feb 13, 2019
@nichtich nichtich added the low priority maybe later label Mar 13, 2019
@nichtich nichtich added this to the 0.8.2 milestone Mar 14, 2019
@nichtich
Copy link
Member Author

To illustrate: In the last row it's unclear why there is nothing in the "to" column:

cocoda-occ

maybe add a mid-long line sich as "---" in the concept scheme column and the to column

@stefandesu
Copy link
Member

This is specific for occurrences, right? Because mappings usually have to have a toScheme value (even if there is no concept in there). So I could check specifically if toScheme is empty and show the line in those cases.

@stefandesu
Copy link
Member

Currently, if toScheme is empty (like in occurrences), it will be set to the target scheme if one is selected. That way, the "mapping" can still be saved directly. But maybe this isn't necessary, I can't really think of cases where this would be useful. I'd suggest to remove that feature and just show a line to indicate an empty target.

@nichtich
Copy link
Member Author

In the example given above the value of toScheme seems empty, although it might be set to the current target scheme internally. At least the To row should be indicated as explicitly empty by a line.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
low priority maybe later user experience Usage should be fun and easy
Projects
None yet
Development

No branches or pull requests

2 participants