hypertopic / lasuli Goto Github PK

View Code? Open in Web Editor NEW

12.0 12.0 4.0 6.93 MB

Social annotation for qualitative analysis

Home Page: https://hypertopic.org/lasuli

License: GNU General Public License v3.0

CSS 4.24% JavaScript 95.02% HTML 0.74%

qualitative-analysis social-annotation

lasuli's People

Stargazers

Watchers

Forkers

slals florentpergoud franck-eyraud triinuerik

lasuli's Issues

"Dotted" highlights

While it happens everytime on Cassandre. It can be reproduced on a very simple Web page:

<html><body>
  <p><b>This is bold.</b> <i>This is italic.</i></p>
</body></html>

Selecting "bold. This is" results in:

Moreover, the highlight is one character longer for every break.

ff5

hi this looks really useful i hope it will be updated
on ff5 a dialog says cannot install
"incompatible with firefox 5.0"

Opening a new Firefox window...

... cause LaSuli to load topics and fragments several times.

http://benel.tech-cico.fr/bugs/lasuli_duplicates_bug.m4v

Print the text with highlights

Several students of mine expressed the need for printing the highlighted text.

Create a more general topic

For example, if S1 and S2 are selected, find common father topics T (if any) then we will have a new topic G so that: T->G->S1, S2

There are of course workarounds, but this feature (in Porphyry) was the
proof that we designed the software for bottom-up analyses and not only for
top-down analyses (like other CAQDAS software).

http://www.hypertopic.org/images/0/0a/Text_bottom-up4.png

Missing slash on default settings

Highlight a text fragment with a given topic

Seeing "immediately" what others are doing on the same page and viewpoints

When Firefox parallel and asynchronous computing mechanisms are stable enough,
replace the polling system with a notification system.

Note: To reduce the opened connections on the server, it is is probably better to implement the "filters" (on opened item and viewpoints) client-side rather server-side.
Note on the note: Then the cache may be reset by the observer rather than by the RESTDatabase itself.

Topics should not appear as categories...

See https://sourceforge.net/tracker/?func=detail&aid=3152564&group_id=258578&atid=1127174

Topics and fragments are loaded for every opened windows

Reproduction :

Open in Firefox :
- http://cassandre.hypertopic.org/text/IF14/0df56d1f70eee373461ae249350008f5
- http://www.google.fr/
- another web page
Open the viewpoint tab in LaSuli

Add the current site to the white list of analyzable Web sites

Despite our warnings, some users continue to keep LaSuli opened while browsing sites they don't want to analyze.

This is a double concern:

for users' privacy (Hypertopic services administrators can see users' browsing history),
for services stress (100 users doing requests every 5 seconds all day long).

This could be fixed with a white list of analyzable Web sites in LaSuli settings:
the first time a user would like to see analyses on a site, he would allow LaSuli to do so.

Create a viewpoint

Highlights containing a sequence of spaces are shorter than intended

Reproduction scenario 1

Open the following TXT file (with two spaces between mode and antique):

Le soleil résonne sur le mode  antique dans le chœur harmonieux des sphères

Highlight mode antique.

What is highlighted is really mode antiqu (without the trailing e).

Unwanted interactions between highlights and document structure

For unknown reasons, LaSuli generates a very deep structure of spans (10 levels) on the creation of an highlight (screenshots will be sent by e-mail).

This could be the cause of two different bugs:

one on the page layout (some rows are too much indented),
the other on the display of fragments (the highlighted text is only a part of the the text used in the name).

Topic drag and drop in the tree view

So that they can be moved as a child of another topic (or in the containing box).

Compatibility with Firefox version 10

As reported by @christophe-lejeune, version 10 of Firefox prevents LaSuli from creating an highlight.
Argos logs show that the PUT method to the item was never sent.

Possibly related behaviors:

When doing the same thing in version 9, the password is asked while it is already defined in the config panel.
Note that PUT methods related to viewpoints are not affected.
Note also that there seems to be no effects of the presence of a secondary service in the config.

Read the current page with ALL its highlights

Because highlights are from different and incompatible viewpoints, the color is:

either the same for all (i.e. yellow as in LaSuli v2),
or depends from the viewpoints (not the topics).

Contrary to v2, the display is not automatic. The user has to click the extension button before highlights are shown.

Here is a TODO list to achieve this:

When the user clicks, modify the page (e.g. with the number of fragments) [messages between scripts].
When the user clicks, display all highlights in the text with a single colour [highlights overlay algorithms from the research paper],
When the user clicks, display all highlights in the text with a colour corresponding to the viewpoint [colors cycle formula, and colors addition on overlays],
When the user clicks, display also a side panel with the mapping between colors and viewpoints titles [reactjs side bar, async requests to the corresponding viewpoints].
When the user clicks, in the side panel display also the other viewpoints used in the corpus [async requests to the corpus, filter, and async request to the corresponding viewpoints].

Exception on topic deletion

Error message whereas the topic is really deleted.

Geographic map highlighting

Highlight geometrical objects on a vectorial geographical map (GeoMap? TopoMap?).
Getting the map directly from a service like OpenStreetMap and zooming it would be a plus.

Switching to another Firefox tab...

... closes LaSuli viewpoints tabs.

http://benel.tech-cico.fr/bugs/lasuli_tabs_bug.m4v

Get examples of a topic before using it

There could be tooltips on topics in LaSuli contextual menu that would list a few fragments (3?) from other documents as examples.

Because it must not be confused with a submenu, the background should be of a different color (e.g. yellow) and it should include a title (e.g. "Examples").

Service identification shouldn't be based on its implementation

It should rather be based on a JSON static payload.

For example:

{"service":"Cassandre"}

Note: This payload could include other attributes too (revision, etc.).

Highlights offsets on adding new highlights

Contrary to what we thought earlier, this bug has nothing to do with HTML page structure, it can be reproduced with a simple TXT file:

 Le soleil resonne sur le mode antique dans le choeur harmonieux des spheres.

Highlight in the following order:

choeur
harmonieux
soleil

When soleilis highlighted, harmonieuxis offset.

Now highlight:

antique

You can see that harmonieux gets more offset.

Then highlight:

spheres

Now refresh the page. You can see that the offset of harmonieux was just a visual bug, but that spheres was created with incorrect coordinates.

Workaround

A workaround to this major bug is to refresh the page as soon as an offset appeared. Otherwise further highlights will be faulty.

"Natural" color blending

Replace substraction with average in order to have more "natural" color blending.
This will prevent blends to get darker and darker.

Note: This is equivalent to alpha blending with alpha=0.5

How to see debug messages

Dear Chao,

I don't succeed in displaying LaSuli debug messages...

In 'about:config', I set 'extensions.lasuli.log.level' to 'Debug' but I cannot see anything related to LaSuli in the Web console or in Firebug's.

What is missing in my settings?

No more contextual menu in Firefox 43

While functioning in Firefox 42 (previous version), the categorize with Lasuli item (in the document contextual menu) is not shown anymore in Firefox 43 (current version).

Get details about a corpus viewpoint

Contrary to v2 where listed viewpoints were user's ones. They will be based on the corpus.
👍 Pros: No need to assign manually every student to the class viewpoint.
👎 Cons: IF14 corpus is HUGE. This will take time to load it.

Contrary to v2, because viewpoints names are not always well chosen, viewpoints will:

display the number of related highlights in the current page,
use the same color used for highlights in the page.

As in v2, once selected a viewpoint should display:

its topics,
its related fragments in the text (with a color for every different topic)
its related fragments in the margin (beneath the topic).

Register also existing corpus

The problem occurs when tagging or highlighting a resource.

When the item exist on a secondary server, an item and a corpus are also created on the primary server. The problem is that the user is NOT registered to it.

The user should be registered the same way as when the resource doesn't correspond to any item and a "bookmark corpus" still not exist.

User experience on the viewpoint tab

For now, the viewpoint tab is split up in three incoherent edition spaces:

the keyword panel (for tagging an entire document with a topic),
the analysis category panel (for creating, renaming, removing a topic, displaying fragments related to a topic, removing a fragment, or moving a fragment from a topic to another one),
the viewpoint window (opened on clicking + next to "keyword") for creating, deleting, moving a topic, but also to tag the entire document with a topic.

The idea would be to replace this with only two modes:

a simplified mode with only what is related to the document,
a complete mode with all that could be used on this document.

Both could be used for edition, both could be used for topics on a complete document (a.k.a. "keywords"), topics on a fragment (a.k.a. "analysis categories").

Duplicated value for an attribute

It appears that sometimes, when we add an attribute to an item the value is duplicated, moreover the system is then unable to remove this attribute.

It seems that the issue is related to the remote server. When I test this feature with my local server, this issue is vanished...

Siblings topics should be sorted alphabetically

... in the tree view.

No more highlights in Firefox 45

While functioning in Firefox 43 (current stable version), highlights are broken in Firefox 45 (current alpha version).

The yellow and mixed colored highlights are not shown anymore.

Firefox 20 incompatibility

Cannot input the key of an attribute at creation

@SlaAls There seems to be an unintended interaction between creating and editing an attribute.

Reproduction scenario

Create an attribute (with a key and value).
Edit the attribute value (the key is not editable as intended).
Create another attribute: the key is still not editable!

Workaround

Close the sidebar.
Open it again.

First topic of an item mistakenly used as a name

For no apparent reasons, when a new item is tagged with a topic, the topic name is also used as the name of the item.

While it could appear to be a good idea, it's not: a name is usually chosen to be distinctive whereas a topic is supposed to be reused for other items.

Invalid owner for viewpoints

When LaSuli is used by students, viewpoints owners are sometimes false:

{
  "_id":"67ca5e52a936fd8998a2bfc6cd85a24c",
  "_rev":"2-68d1c849a39c49db82f5162e3b47a459",
  "viewpoint_name":"argos2.hypertopic.org",
  "users":["guest"],
  "topics":{
    "36b275af05d7480bb3aabdf1a09c5535":{"broader":[],"name":"No name"}
  }
}

Argos logs reveals that the faulty payload may have been built with a faulty login and then sent again with a corrected one:

401: guest (78.251.55.58) PUT /67ca5e52a936fd8998a2bfc6cd85a24c HTTP/1.1 @ 01/Jan/2012:09:34:25 +0100
201: siqi.duan (78.251.55.58) PUT /67ca5e52a936fd8998a2bfc6cd85a24c HTTP/1.1 @ 01/Jan/2012:09:34:30 +0100

This is probably due to the fact that when LaSuli encounters a 401 error, the login and password are asked again. I suspect that the payload is then kept as it was.

Note:

Porphyry already knows how to compute picture fragments co-occurrence (see code),
Steatite already knows how to create a thumbnail from a picture fragment (see code).

Highlight exceeds on the whole span

It can be reproduced on a very simple Web page:

<html><body>
  <p><b>This is bold.</b> <i>This is italic.</i></p>
</body></html>

Selecting "This is bold. This" results in:

Create a topic

Cannot highlight a word

It can be reproduced on a very simple Web page:

<html><body>
  <p><b>This is bold.</b> <i>This is italic.</i></p>
</body></html>

Select the second "This" and try to highlight it. It cannot be done.

Workaround: Select also the space before or the space after.

hypertopic / lasuli Goto Github PK

lasuli's People

Stargazers

Watchers

Forkers

lasuli's Issues

Reproduction scenario 1

Workaround

Reproduction scenario

Workaround

Recommend Projects

Recommend Topics

Recommend Org