Planning[edit]

	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

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

R1[edit]

Login /Logout
Display
Browsing
Search
Metadata Sets

Functional Prototype for R1

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

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

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.

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 metadata profile (i.e. add/remove metadata from a list provided by the MPDL + create your own metadata fields)
  - Metadata profile should be under version control, therefore with a pending/publish life cycle. Should it be done in the first step: To be clarified --Bastien 12:36, 19 May 2010 (UTC)
  - Add/Remove Metadata from a list provided by the metadata
  - Add/Remove own metadata fields (with a predefined type: String, Integer, ...)
  - Add/Remove a controlled vocabulary to a metadata via Cone data (plus Linked data (linking between cone and e.g. "Geonames"))
2. Create/update content-model out of metadata profile (done automatically via 1)
3. Create/update default screen configuration out of metadata profile (done automatically via 1)

Collection Management:
1. Create collection with one md profile (editor for the creation of a configurable collection schema) and a default style

How will the md pofile be related to the collection? (item, md record field, other?) : Should be via content-model --Bastien 10:01, 19 May 2010 (UTC)

1. Define Collection md profile
  - Publication metadata profile + specific metadata profile for entry point style info?
  - Specific metadata profile, to be defined
2. Collection Entry point page (md record for entry point information should be specified)
  - View entry point via direct link
  - Edit/Customize style of entry point

Upload (data ingest by the user):
1. Upload images for one collection
  - via selecting a folder
  - via selecting a zip
2. Create thumbnails and web resolution and upload all 3 resolutions
3. Extract technical metadata (IPTC [1])
4. Create items with technical metadata (filename, size, ...) but empty metadata record
5. (Optional) Scan filename
  - define pattern (how filename should look like)
  - Define parsing: which metadata should be mapped and how
  - Create items with technical metadata (filename, size, ...) with populated md-record

Metadata Editing:
1. Batch editing
  - Filter the images based on already available metadata values (e.g. technical metadata: date creation)
  - Select images
  - Edit metadata values (retrieved from related schema) of selected images from edit mask (metadata are stored in item metadata record)
2. Edit metadata of a single image

Browsing:
1. Browse by collection
  - Browse pictures within one collection (sorting by the md set)
2. Browse by albums
  - Browse pictures within one album (sorting is not possible when the pictures within one album use different metadata profiles)
  - Filter within the album (e.g. by metadata profile --> now sorting is possible)

Search:
1. General free text search (any metadata value, either in album, picture or collection)
2. Search for collections (e.g. which collection has a metadata field called temperature)
  - Do simple search
3. Search for albums (album metadata)
  - Do simple search
4. Search for pictures (metadata values)
  - Select a metadata set / collection
  - Do advanced search for the selected metadata set

Researchers homepage (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?)

Isn't this already provided, at least with no metadata? Just do a right mouseclick and download the pic.

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

PIDs are now integrated

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.

Faces Scope

Contents