-
-
Notifications
You must be signed in to change notification settings - Fork 29
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
entry "unreadness" #1025
Comments
That information would need to be tracked in each project's database; I think it was a mistake to put the |
Then when building the list view, we'd do a Mongo query on |
This sounds like a nice feature! If implemented, I think it would be good to be able to bulk-edit the "viewed status". For example, a user could mark all 7000 entries as viewed upon import, and then only see the new unread entries as other users create or edit them. Or, mark an individual entry as "viewed" or "unviewed". Also, I think it would be very useful to be able to search for entries that I have interacted with and that have since been interacted with my other users. Not sure where the best place to put that in Github would be. |
@alex-larkin You can describe the desired behavior of your idea in a card, and then place it in the ideas column on the features board that Billy created. |
Will do! Distinguishing unread entries: They could have a slightly different background color (like notes in Paratext). |
The idea I listed in #1013 (comment) (a "Needs work"/"Completed" status for entries along with a counter to track how many are done so far) also relates to this "unreadness" idea, at least a little. Because if we use a background color to mark unread entries in the list view, perhaps we could also include some kind of background color or highlight to mark entries with the "Needs work" status in the list view as well. |
Just an idea:
Keep track of entries that have been seen by the user. Distinguish unread entries in the list somehow.
The text was updated successfully, but these errors were encountered: