Talk:Faces Implementation

MPDL,Faces,FIZ

Steps in development:

Prototype uses FW instance on server: zim02.gwdg.de

November 2007

 * create Faces context [Bastien]
 * create FaceItem content model [Bastien]
 * decide on FaceItem descriptive metadata (use of standard namespace) [Kristina]
 * implement XSD for FaceItem descriptive metadata [Bastien, check with Matthias]
 * create xml files with data in accordance with item.xsd and descriptive metadata [Matthias]
 * upload xml data to the FW instance on zim02.gwdg.de [Bastien]
 * Display and browsing (registered user access) supports following functionalities:
 * View lists of pictures [Bastien]
 * Navigation in lists by using a paginator
 * Select / deselect pictures for export
 * View picture details [Matthias]
 * Display of all information/attributes of one picture
 * basic user management (registered user, administrator user).
 * registered users: should see all metadata and all face items

HowTo and directions

 * General: use framework installation on zim02.gwdg.de
 * To create context: use Admin interfaces on zim02.gwdg.de (remind Natasa or Robert: should be before switched to work with FW installation on zim02.gwdg.de, use developer Wiki to see exact Ip and instances)
 * to implement XSD for FaceItem descriptive metadata: should be alligned with the other metadata profiles defined and should be in the repository with other metadata profiles defined
 * Core services specification is available for each build/release
 * to create FaceItem content model (contacted FIZ, monitor issue in Bugzilla)
 * to create FaceItems: use ItemHandler service and Rest or Soap interface, prepare Item examples in accordance with the item.xml schema available at eSciDoc core service schemas, use ItemHandler.create (for SOAP) or ir/item/PUT (for REST) methods to create items (note: there are additional methods for uploading of the content of the image check the specification for more details). When picture content is uploaded i.e. content component is created for an item, the visibility should be public only for images of known 6 persons. For all other components that represent respective picture content - visibility is "private".
 * an item can be searchable only if it is in state "released". It is originally created as "pending". For these purposes one must use "task-oriented" item handler methods (submit, release).
 * for display and browsing (one must use respective retrieveItem methods ItemHandler and in addition Search and Browse method, check specification for more details)
 * to view picture details one must use ItemHandler method for downloading of binary content (see spec)
 * for basic user management one must use AA Handler methods for login, logout. Test users can also be created either directly via FW interfaces or via GUI Admin interface on zim02 (see above)
 * TODO@Christina: please define exact names of Roles (proposal: let these roles names are "Faces_" needed for the first step and what are their exact rights and privileges (i.e. for registered user, anonymous user and administrator user). When this is finished we need to create these roles for ourselves (or with help of FIZ).

December 2007

 * export items (xml and zip file) [Bastien]
 * baskets, study sets [Bastien, Matthias] (to be detailed later)
 * rework the browsing/displays for public users (Bastien, to be detailed later)

January 2007
Person view/update (administrative interface, to be detailed later) [Matthias] Note: to check if Matthias can rework local solution to work with FW instance.

December 2007/January/Feburary 2008?
Note: note clear as we have no further feedback on digilib - check with FIZ on Digilib.
 * Navigate within one picture
 * Zooming in, zooming out, framing of a zoom area, switching back to see the whole picture
 * Left, right, up and down navigation within the zoomed in picture