View Source

{toc}

h1. Projects and Access Control

* Spaces for each project and shared space\* Each project gets its own "space" (collection) in the DMS. In addition, project members can access the shared collection
* The DMS performs authentication (login) and authorization (determining access rights)
* Every access to RDF is initiated through the DMS, and the DMS passes these additional parameters in every request:\* rights (read-only or read-write)
* named graph (default and one selected project)
* where to store materialized inference (the default or the named graph)\* Access Control administration, new project space creation

h3. {color:#008000}Notes on Alfresco{color}

{color:#008000}Space can be modeled by "site" in Alfresco. Each user can be a member of one or more sites with specific permissions for actions in the sites. Sites can be private (each member should be invited to has access) or public - everyone has view access.{color}
{color:#008000}Each user is authenticated by user name and password. Integration with LDAP is done for QVII.{color}
{color:#008000}Administration UI is available in Alfresco - sites, members and permissions can be managed from administrators.{color}

h3. {color:#3366ff}Notes on Nuxeo{color}

{color:#3366ff}For Nuxeo the collaboration space is called "workspace". Each workspace has members with their access rights as well as folders, blogs, forums, wiki.{color}



h1. GUI framework and navigation

* Static navigation - customizable per project

TBD

* Navigation between linked objects

TBD

* External GUI components

GUI needs to be able to incorporate third-party tools. These can possible include:
\- Client-server tools with remote servers and HTML/JavaScript client
\- JavaScript component libraries
\- Flash components
These components should be able to share data with the rest of the GUI (e.g. perform specific operations on the selected image)

* ResearchSpace Tools

In addition to third-party tools, we would need to provide our own as well. One example is RS Toolbar.
\- They should be container-independent
\- They should be probably implemented using plain HTML, SCC, JavaScript and Ajax
\- They should share data with the rest of the GUI

* Customized and externalized search mechanism

\- Custom search criteria screens and result screens
\- Full-text search would be performed by OWLIM
\- Semantic search would be performed by OWLIM

h3. {color:#008000}Notes on Alfresco{color}

{color:#008000}Static menus can be added, moved, edited etc. They can be specific for a site or for all sites.{color}
{color:#008000}New pages can be embedded including links to other pages. The context of the application can be accessed.{color}
{color:#008000}Search should be reimplemented to use OWLIM (incl. indexing, highlighting etc.){color}

h3. {color:#3366ff}Notes on Nuxeo{color}


h1. Collaboration and social networking

* Management of Wikis, Blogs and Discussion forums: create, edit, comment, etc.
* Personal messages (BaFO)
* Integration with Search Engine -- where the team members will be able to search in all blogs, wikis and discussion forums.
* Link and locate data, documents and assets to wikis, blogs and discussions. Only linking to a whole blog or wiki page will be supported.
* Integration with ResearchSpace Toolbar, from where will be started RS Data Basket and the Research Tools

h3. {color:#008000}Notes on Alfresco{color}

{color:#008000}Community edition wiki does not work well with IE. The blog and the discussions are very very basic. They are not connected to documents (discussions, blogs, wiki){color}
{color:#008000}Personal massages can be implemented by tasks. They can be used but don't have the typical functionality for messages.{color}
{color:#008000}Links to data currently not supported.{color}


h3. {color:#3366ff}Notes on Nuxeo{color}

{color:#3366ff}Threaded comments can be added to documents.{color}


h1. Document and Asset upload

* DMS will support document and digital asset libraries, where all types of documents can be uploaded. Support of Document Library Structure.  The library structure is predefined and automatically created with the creation of each new project.
* Special permissions are set to team members
* Support of common user actions on documents, such as like: upload new version, edit, download, print, copy to other folder, move, manage permissions, etc.
* Support of optional and mandatory metadata for each newly uploaded file (images, documents).
* Association of keywords to each document
* Version control of changes in document content and metadata
* Support Lightbox (thumbnails) for image contents

h3. {color:#008000}Notes on Alfresco{color}

{color:#008000}For QVI this functionality is implemented - a.k.a "initialization of site".{color}
{color:#008000}Permission can be managed at folder or even document level. There is 4 basic roles and each user can take on of those roles. Each role is linked with specific permissions but some permissions are connected and can not be managed separately.{color}
{color:#008000}Print action is custom and implemented for QVI{color}
{color:#008000}Optional and mandatory metadata is supported in Alfresco. If we need to change metadata fields, this is done programatically.{color}
{color:#008000}Keywords supported by tags.{color}
{color:#008000}Version control is supported for content but not for metadata. Version comparison is not supported.{color}
{color:#008000}Lightbox to be checked. Thumbnails supported{color}

h3. {color:#3366ff}Notes on Nuxeo{color}

!nuxeo.jpg|thumbnail,border=1!

{color:#3366ff}Metadata fields can be modified programatically, see{color} {color:#3366ff}[here|http://doc.nuxeo.com/display/DAMDOC/Metadata+Customization]{color}{color:#3366ff}. By default Nuxeo supports Dublin Core schema. Metadata can be optional and mandatory.{color}



h1. Data Annotation, Input Editing & Version Comparison

* Online Data Entry

Stage3: simple hard-coded forms for entering information that occurs most often in museum systems.
BaFO: Generation is suggested from RDF or XSD.
Data Annotation
TBD

* Version Comparison

Stage3: The required capability for Versioning of every field means that each RDF data property is complemented with a list of object properties that carry version info (who, when and maybe why made the change). For example, given a data property hasNumber, we can complement it with  hasNumber_history and end up with triples like this (using Turtle notation):
obj hasNumber "5" ;
   hasNumber_history \[creator: "Vladimir"; date: "2011-01-05"; oldValue: "4"; newValue: "5"\],
                                   \[creator: "Ivan"; date: "2011-01-01"; oldValue: "3"; newValue: "5"\].
Some rules for finding and using the latest version are required.
TBD How about documents versioning?

h3. {color:#008000}Notes on Alfresco{color}

{color:#008000}Online Data Entry: similar functionality done in QVI project for master lists. Forms are made with Yahoo forms - integrated with Alfresco share. Yahoo forms are easy to configure and extend.{color}


{color:#008000}Version Comparison: No version comparison available in Alfresco.{color}




h3. {color:#3366ff}Notes on Nuxeo{color}

{color:#3366ff}Document annotation:{color} {color:#3366ff}[http://doc.nuxeo.com/display/DMDOC/Annotations]{color}

h1. Dashboards

A dashboard is a configurable area where a user can select from various pre-configured layouts and construct their own page from a list of pre-configured components. Both Nuxeo and Alfresco support multi column layout templates where by drag and drop could be added or removed dashlets on the dashboard. The list of dashlets may be configured.
Stage 3

* Project Administrator Dashboard
** Support of project profile (name, description, project Manager, project team members)
** Latest activities in a project -- in terms of new or updated content (documents or assets), new blogs, forums, wikis
** Documents and Assets recently modified
** Manage User permissions

* Project Team Member Dashboard
** View information about project profile
** Update personal user profile -- with passwords, name and contact details

BaFO: Dashboard personalization may be required

h3. {color:#008000}Notes on Alfresco{color}

{color:#008000}Project Administrator Dashboard{color}
* {color:#008000}Support of project profile (name, description, project Manager, project team members) - Site profile dashboard in Alfresco{color}
* {color:#008000}Latest activities in a project -- in terms of new or updated content (documents or assets), new blogs, forums, wikis - RSS Dashlet in Alfresco - could be added new feeds for integrated forums, blogs and wikis.{color}
* {color:#008000}Documents and Assets recently modified - Recently Modified Documents dashlet in Alfresco (only for Documents){color}
* {color:#008000}Manage User permissions - Currently in Alfresco this is a separate menu, not a dashlet{color}

* {color:#008000}Project Team Member Dashboard{color}\*\* {color:#008000}View information about project profile - Site profile dashboard in Alfresco{color}\*\* {color:#008000}Update personal user profile -- with passwords, name and contact details - Currently in Alfresco this is a separate menu, not a dashlet{color}

{color:#008000}BaFO: Dashboard personalization may be required - supported in Alfresco{color}



h3. {color:#3366ff}Notes on Nuxeo{color}


h1. Images -- view, annotate, deep zoom, references to

We would probably use a third-party tool for high-resolution images storing and serving. Still, we need to decide what to do with other images that are web-friendly (thumbnails etc.)
Stage 3: only rectangular shapes would be supported when parts of the image are annotated.
We need to be able to refer to images in wiki, discussions etc.
• Design strategy for storing annotations in the ResearchSpace repository, indexing them if necessary
• Build data selector/mapper to map repository search results into the image display
• We'll have image annotation of small images only.
BaFO: Annotation at arbitrary zoom level is suggested

h3. {color:#008000}Notes on Alfresco{color}

{color:#008000}Stage 3: only rectangular shapes would be supported when parts of the image are annotated.{color}
{color:#008000}We need to be able to refer to images in wiki, discussions etc. - there is no ability to refer to documents in wiki and discussions in Alfresco{color}


{anchor:img-zoom-nuxeo}

h3. {color:#3366ff}Notes on Nuxeo{color}

{color:#3366ff}{_}{+}Jana{+}{_}{color}{color:#3366ff}: Nuxeo DAM: deem zoom + image annotation:{color} [http://doc.nuxeo.com/display/DAMDOC/Annotate+assets]















{color:#3366ff}Nuxeo DAM is a separate product but may be installed together with Nuxeo DMS and share same repository (docs and images). Nuxeo DAM relies on ImageMagick binaries for tiling/deep zoom - much like the way OpenOffice is used to handle MS Office documents (both in Alfresco and Nuxeo). Not sure this scales good enough. I think they also might be doing it (tiling) on the fly - but need to check this.{color} {color:#3366ff}{*}{+}Edit{+}{*}{color}{color:#3366ff}: See answers{color} {color:#3366ff}[here|http://answers.nuxeo.com/questions/260/nuxeo-dam-image-zoom-and-annotation-questions]{color}{color:#3366ff}.{color}



{color:#3366ff}GUI uses Ajax for tiling and implements annotation at different levels.{color}

{color:#3366ff}Only rectangular shapes are supported. User cannot zoom out beyond original size. Zoom in/zoom out via mouse wheel is not supported. Moving view area via dragging is not supported. Bottomline: it provides basic functionality but GUI is clumsy and the solution may not scale well enough for many users and very large pictures.{color}

{color:#3366ff}See{color} !nuxeo-dam-image-annotation.jpg|thumbnail,border=1!

{color:#3366ff}When annotation region is not entirely into view area, it is not shown.{color}






h1. CMS interfaces to RDF for metadata exchange

Stage3: When a content item is inserted in the DMS, some standard metadata is captured:
• The user may be asked to enter some data (e.g. Title, Author)
• The repository may capture additional metadata (e.g. EXIF image information, creator, date created)
All this metadata will be transferred automatically to RDF, so that the RDF repository has complete metadata about all objects.

h3. {color:#008000}Notes on Alfresco{color}

{color:#008000}• The user may be asked to enter some data (e.g. Title, Author){color}
{color:#008000}• The repository may capture additional metadata (e.g. EXIF image information, creator, date created){color}

{color:#008000}All above supported from Alfresco. Also custom metadata can be added according to the type of the content (aspects in Alfresco){color}



h3. {color:#3366ff}Notes on Nuxeo{color}


h1. Data Basket

The ability to select and preserve work for subsequent usage by the same researcher or by his collaborators is a crucial element of any research activity.
Stage3:
• This Research Tool be able to collect information acquired in the process of navigating through the ResearchSpace in a special location similar to “carts” of the online stores.  The technology of moving data from the Research Tool into these “carts”  is by dragging and dropping them. The carts will collect information in a tabular format with columns for the data themselves and with columns  for metadata regarding their insertion  in the data basket (time, author, comments..)
• The data transferred into the data basket will preserve their semantic format, URIs, and will provide direct access to all information about them stored in the semantic repository.  This includes links to images and documents.
• A search can be saved and will be regarded as an object and included into the tables of the data basket.

h3. {color:#008000}Notes on Alfresco{color}


h3. {color:#3366ff}Notes on Nuxeo{color}