Difference between revisions of "Faces Scope"

From MPDLMediaWiki
Jump to navigation Jump to search
Line 42: Line 42:
* GUI V2
* GUI V2
[https://zim01.gwdg.de/repos/smc/trunk/04_Design/03_GUI_Design/02_interface_conception_and_design/02_01_Prototyping/HTML_Prototyp/FACES_R3.5/index.html Functional Prototype for R3.5]
[https://zim01.gwdg.de/repos/smc/trunk/04_Design/03_GUI_Design/02_interface_conception_and_design/02_01_Prototyping/HTML_Prototyp/FACES_R3.5/index.html Functional Prototype for R3.5]
=== R3.x.1 ===
* [[Faces_Album_Management#Sharing_of_an_album|Sharing of albums]] with other users (incl. user privileges, tracking of changes)
* [[Faces_Note_Pads|Note pad]] for albums
* [[Faces_Album_Management#UC_FAC_AM_12_Copy_album_content|Copy album content]]
* [[Faces_Album_Management#UC_FAC_AM_13_Merge_album_content|Merge album content]]
* Cone entries for album editors and organizations (cone integration)
* Download of a single picture (and it's MD?)
* Fine granular access rights for released items (per picture)
* Simplified breadcrumb navigation (Last Album View, Last Image View)
* Screencast
=== R 3.x.2  ===
AIM: Make the FACES software more interesting for other institutes!
* Editor for the creation of a configurable collection schema
*# Integration of controlled vocabulary (cone)
*# Linked data (linking between cone and e.g. "Geonames")
*# Definition of data types (e.g. string, data)
* Collection portal (one entry point for all collections)
* Data and metadata ingest by user (zip+ecxel)
* Batch tagging (assignment of new metadata to the items)


=== R 4.0  ===
=== R 4.0  ===
AIM: Upload of collections
AIM: Upload of collections to make the FACES software more interesting for other institutes!
* Surrogate item implementation
* Surrogate item implementation
* Metadata Profile management:
* Metadata Profile management:
Line 75: Line 54:
*# Edit metadata values of selected images from edit mask
*# Edit metadata values of selected images from edit mask
* Collection management
* Collection management
*# Create collection with one md profile
*# Create collection with one md profile (editor for the creation of a configurable collection schema)
*#* Integration of controlled vocabulary (cone)
*#* Linked data (linking between cone and e.g. "Geonames")
*#* Definition of data types (e.g. string, data)
*# Upload/remove images in collection
*# Upload/remove images in collection
*# Browse collection
*# Browse collection
*# Search Collection
*# Search Collection
* Upload:
* Upload (Dataingest by user):
*# Select a collection
*# Select a collection
*# Select folder with images to be uploaded
*# Select folder with images to be uploaded (folder or zip)
*# Create thumbnails and web resolution and upload all 3 resolutions
*# Create thumbnails and web resolution and upload all 3 resolutions
*# Create items with technical metadata (filename, size, ...) but empty metadata Record
*# Create items with technical metadata (filename, size, ...) but empty metadata Record
* Search for Container (search for album and collection)
* Search for Container (search for album and collection)
* Wordpress plugin
* Wordpress plugin
* Collection portal (one entry point for all collections)


=== Further Requirements===


=== Further Releases ===
* [[Faces_Album_Management#Sharing_of_an_album|Sharing of albums]] with other users (incl. user privileges, tracking of changes)
* [[Faces_Note_Pads|Note pad]] for albums
* [[Faces_Album_Management#UC_FAC_AM_12_Copy_album_content|Copy album content]]
* [[Faces_Album_Management#UC_FAC_AM_13_Merge_album_content|Merge album content]]
* Cone entries for album editors and organizations (cone integration)
* Download of a single picture (and it's MD?)
* Fine granular access rights for released items (per picture)
* Simplified breadcrumb navigation (Last Album View, Last Image View)
* Screencast
* Integration of [[Digilib]]
* Integration of [[Digilib]]
*# in a separate window
*# in a separate window
Line 95: Line 87:
* Normstudy
* Normstudy
* Integration of the extended pictures from Rostock
* Integration of the extended pictures from Rostock
=== Misc ===
* Usage of an online application form (see [[Faces_User_Management#Further_requirements|Faces User Management]])
* Usage of an online application form (see [[Faces_User_Management#Further_requirements|Faces User Management]])
* Persistent Identifier (PID) - depends on when the gwdg can provide this functionality
* Persistent Identifier (PID) - depends on when the gwdg can provide this functionality
* User Management that can be managed by the institute, not the MPDL (see [[Faces_User_Management#Further_requirements|Faces User Management]])
* User Management that can be managed by the institute, not the MPDL (see [[Faces_User_Management#Further_requirements|Faces User Management]])
* Metadata ingest by user (zip+ecxel)
* Batch tagging (assignment of new metadata to the items)


= Expectations =
= Expectations =

Revision as of 15:03, 5 May 2010

FACES

Scope · Functionalities
Disclaimer and Copyright
Support

Application Profiles
Release Agreement

Specification:
Browse and Display · Search
Albums · Users
Note Pads · Versioning

Related Projects:
Imeji

edit


Planning[edit]

The prototype of Faces will be developed in several steps (releases). In each release, the following functionalities will be implemented.

Checkmark.png R1[edit]

  • Login /Logout
  • Display
  • Browsing
  • Search
  • Metadata Sets

Functional Prototype for R1

Checkmark.png R2[edit]

  • Enhancement of the search (age group search functionality, search within an public album)
  • Public (published) albums
  • Selection of Pictures (adding)
  • Multiple sorting
  • Export
  • Help functionality (linking between the help icons "?" within the application and the help page)

Functional Prototype for R2

Checkmark.png R3[edit]

Going productive!

  • User Management (Basic, via Admin solution)
  • Basic statistics
  • Extraction (via jhove) and saving (in a separate metadata file) of technical metadata
  • Display of technical MD
  • Revision of Help (texts)
  • New Home Page for Faces (no special Faces logo, only the MPIB logo)
  • Integration of a blog for the creation of a news box on the start page

Functional Prototype for R3

Checkmark.png R3.2[edit]

Virtual release! - prepare FACES for a generic usage

  • Surrogate items
  • Enabling of generic integration of metadata profiles (NIMS, MPI zur Erforschung multi-religiouser u. -ethnischer Gesellschaften)

No functional Prototype needed for this release, as no 'visible' changes.

Checkmark.png R3.3 (GUI Release)[edit]

  • GUI V2

Functional Prototype for R3.5

R 4.0[edit]

AIM: Upload of collections to make the FACES software more interesting for other institutes!

  • Surrogate item implementation
  • Metadata Profile management:
    1. Create/edit simple md profile (i.e. add/remove metadata from a list provided by the MPDL)
    2. Create/update content-model out of md-profile
    3. Create/update default screen configuration out of md profile
  • Batch metadata editing:
    1. Select one or many images
    2. Edit metadata values of selected images from edit mask
  • Collection management
    1. Create collection with one md profile (editor for the creation of a configurable collection schema)
      • Integration of controlled vocabulary (cone)
      • Linked data (linking between cone and e.g. "Geonames")
      • Definition of data types (e.g. string, data)
    2. Upload/remove images in collection
    3. Browse collection
    4. Search Collection
  • Upload (Dataingest by user):
    1. Select a collection
    2. Select folder with images to be uploaded (folder or zip)
    3. Create thumbnails and web resolution and upload all 3 resolutions
    4. Create items with technical metadata (filename, size, ...) but empty metadata Record
  • Search for Container (search for album and collection)
  • Wordpress plugin
  • Collection portal (one entry point for all collections)

Further Requirements[edit]

  • Sharing of albums with other users (incl. user privileges, tracking of changes)
  • Note pad for albums
  • Copy album content
  • Merge album content
  • Cone entries for album editors and organizations (cone integration)
  • Download of a single picture (and it's MD?)
  • Fine granular access rights for released items (per picture)
  • Simplified breadcrumb navigation (Last Album View, Last Image View)
  • Screencast
  • Integration of Digilib
    1. in a separate window
    2. fully integrated in the Faces GUI
  • Versioning: View album event log
  • Normstudy
  • Integration of the extended pictures from Rostock
  • Usage of an online application form (see Faces User Management)
  • Persistent Identifier (PID) - depends on when the gwdg can provide this functionality
  • User Management that can be managed by the institute, not the MPDL (see Faces User Management)
  • Metadata ingest by user (zip+ecxel)
  • Batch tagging (assignment of new metadata to the items)

Expectations[edit]

Expectations MPI B[edit]

  • Faces will be a service based on the eSciDoc infrastructure for publishing digital images (incl. a user management for all users who work with faces).
  • The institute’s and department-specific corporate design will be visible in the web design of the solution.
  • The content of the collection Faces will be digitally preserved and persistently identified.
  • The data from the currently available Faces database will be integrated.
  • The data of the collection Faces is not published as open access, except for the data of the six predefined persons who gave explicit publishing permission.
  • Faces will be a closed collection, so the import of further images is not possible once the application is running.
  • The application will support the future integration of further attributes (e.g from the normstudy).
  • Once the application is running, it can't be changed without the permission of the institute.
  • The MPI has fully administrator rights for the application.

Expectations MPDL[edit]

  • Faces will be delivered as an open source self-contained web application, which can be installed and run with predefined standard set-up.
  • The MPDL will use the FACEs solution as showcase for demonstrating possible research data scenarios based on the infrastructure. The institute's staff will support respective outreach activities by reporting on their experiences.
  • The MPDL has access to the root account of the application for administration purposes.
  • The data of Faces will be hosted at the MPDL (and/or its partners like the GWDG), who are also responsible for the server administration. Details will be defined in a service level agreement.