aerugo / bbu Goto Github PK

Allow a reading user to store annotations in their annotation collection in the session storage.

If a user is logged in, their collections persist in their account, and they can organize collected annotations in folders.

We want to implement fragment highlighting in the UI.

• Fragments can be identified in posts by toggling "highlighting". When a fragment is highlighted, the rest of the post text turns grey.
• If multiple fragments in the same post are highlighted, they are black, while the rest of the post is grey.
• If nothing is highlighted, then the entire post is black.
• Highlighting is specific to a post. Highlighting only turns the rest of that post grey, not the other posts in the same topic.

A new column is introduced to show the highlight toggles

When highlights are toggled, the rest of the text in the post that is not highlighted turns grey. This transition should be to lower the opacity, and it should happen with a smooth but fast animation.

Highlights are specific to a post - posts above and below are unaffected.

Codes can be updated or removed, either through the codebook or through a code page.

A code edit tool is brought up by clicking the description of a code (if you have the right permissionss), either on the codebook or a code page.

Changes:

• Change hamburger icon to a thinner line-weight, that align with the font.
• Replace code and arrow with simple arrow. Use > arrow from font.
• Remove numbers from codes. (I don't think they are necessary here, the user gets that information anyhow when going to a code, and this way they will explore codes based on interest and not on numbers.)

Folded view:

Unfolded view:

We want to introduce a feature where navigating to a post through a fragment has the following effect:

Changes:

• Move Fragment 2-3 lines down the page.
• Replace post arrow with "From"
• Remove code and network icon.
• Add an extra linebreak before codes.
• Add "Codes:" text above code list.
• Remove numbers in black circles from before codes.
• Add numbers in text after codes, e.g. anger, 27 annotations with 85 connections (@aerugo you can change the exact wording here to suit the methodology better)

Changes:

• Move X to align with hamburger in other views.
• Change X to thinner line weight that follows the general line-weight of the Baskerville font

Logged-in users with the right permissions can add, edit and remove annotations.

Annotation spans can be shifted, multiple codes can be added to the same annotation, comments can be added.

We are planning to implement a modified version of RecogitoJS. See mockups below to see how the annotation tool should look and work.

Select a highlighted fragment by clicking on it once

Clicking on a highlighted fragment brings up the controllers that can be used to shift the span of the annotation-

Double click on a selected fragment to bring up the annotation tool.

If multiple codes belong to the same annotation, the code description is for the last code added.

When codes are selected, the code description is changed.

Note: When codes are added, you select them from an auto-complete dropdown. You can also create a new code by writing a new code into the prompt.

Comments can be added to annotations

Annotations are saved on close

Changes:

• Add ":" after "X fragments refer to this code", ie: "X fragments refer to this code:"

We want to add simple login and user management. We also want to be able to administrate users and set simple permissions.

**Login through the menu. The login screen is a very simple magic link email prompt. **

Admins can see and manage users and permissions.

Admins can invite new users.