compared with
Current by jana.parvanova
on Oct 23, 2012 11:59.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (5)

View Page History
(on)  It makes sense to use same design and implementation as for annotations tags. Currently these are stored entirely in Nuxeo and not in RDF. We suggest that in 3.6 we spend some effort on removing Nuxeo dependencies for annotations, including the tags functionality. Then we can use the same approach and implementation for Data Basket tags.

(/)  Dominic:....
(/)  Dominic (with Jana on Skype, Oct 15): Lets have tags implementation reworked in 3.6 - that is, store tags in RDF and not Nuxeo. Then we will use common implementation for annotations and for data basket.


If items become too many, GUI might get unfriendly.

(/)   Dominic (with Jana on Skype, Oct 15): Lets keep it simple (no pagination) for now and see how users are going to use it. That is, are they going to use Data Basket as Clipboard (probably need to remove oldest items then) or as personal storage (more permanent thing).


h3. (?)   Shorten URL - what is expected exactly there
{jira:RS-954}


h3. (?)  Can we add links to relations (predicates) in Data Basket

The spec says data field can be added. What about predicates (like was-created-by)?

(on)  Dominic (with Jana on Skype, Oct 15): Will think about it but I cannot think of case they would need to store a predicate there.


h3. (?)   Notes on icons (UI mockups) by Vlado

- (on)  rich-text editor that we use is tiny MCE and it uses new browser windows for popups. Are we doing to implement databasket popup like this or it will be part of the page as a simple div tag? If it is new browser window - styling should be changed (there are minimum width of 1200 pixel for the popup, margin for the whole databasket table and so on). If it is part of the page as div it will look a little inconsistent with the other buttons of the tiny MCE. Still, we suggest we keep it as div.
- (on)  which will be the data basket sort criterias? We suggest type, date (default), title. The sort is by a single field
- Icons for data basket element types are way more than tool history ([https://confluence.ontotext.com/download/attachments/26187321/RS_dataicons.jpg?version=2&modificationDate=1345207775000] and tool history has only 3 items). If one of the used bookmarks from databasket is selected then new history element will be inserted in one of the three history options. They have similar images as databasket icons and it may be confusing if data field/data annotation and museum object bookmarks will be added as an element in data annotation tool.

h3. (?)  If the user selects an item to add in the databasket, and such item is already there, how do we inform the user?