Difference between revisions of "Faces"
| Line 40: | Line 40: | ||
* Attribute export as CSV | * Attribute export as CSV | ||
''' | '''Image Resolutions''' | ||
* 819 x 1024 | * 819 x 1024 | ||
* 2835 x 3543 | * 2835 x 3543 | ||
* | * Automatically generated thumbnails | ||
| Line 56: | Line 51: | ||
=== Aim | === Aim === | ||
Wesentlich wird es – neben der Einbindung in die eSciDoc-Architektur – darum gehen, die bisherigen "Attribute" auf der Ebene des einzelnen Bildes zu ergänzen um weitere, standardisierte Metadaten (ggf. [http://www.loc.gov/standards/mets/ METS]) , und ein Rechtemanagement zu implementieren, d.h. differenzierte Zugriffsrechte zu ermöglichen. Dabei muss die Datenbank strukturell offen sein für die Aufnahme weiterer (Beschreibungs-) Daten – wie etwa von der Normierungsstudie zu erwarten (expressed by UF). | Wesentlich wird es – neben der Einbindung in die eSciDoc-Architektur – darum gehen, die bisherigen "Attribute" auf der Ebene des einzelnen Bildes zu ergänzen um weitere, standardisierte Metadaten (ggf. [http://www.loc.gov/standards/mets/ METS]) , und ein Rechtemanagement zu implementieren, d.h. differenzierte Zugriffsrechte zu ermöglichen. Dabei muss die Datenbank strukturell offen sein für die Aufnahme weiterer (Beschreibungs-) Daten – wie etwa von der Normierungsstudie zu erwarten (expressed by UF). | ||
| Line 63: | Line 58: | ||
=== Functional Requirements === | === Functional Requirements === | ||
''' | '''Browsing''' | ||
* Browse photo collection | * Browse photo collection | ||
* View photos and their attributes | * View photos and their attributes | ||
* Select | |||
'''Searching''' | |||
* Select photos according to their attributes (advanced search) | |||
* Manually refine selection | * Manually refine selection | ||
'''Export''' | |||
* Export result set including attribute data | * Export result set including attribute data | ||
'''Data Enrichment''' | '''Data Enrichment''' | ||
* Adding of attributes to images, also from external data | * Adding of new attributes to images, also from external data via ingestion or one by one (new attributes have to be introduced to all images, also if the values are not available for all of them) | ||
* Annotations of data sets (e.g blocking of a data set) | * Annotations of data sets (e.g blocking of a data set) | ||
* Maybe integration of administrative data (e.g. birthday, contact details) in an administrative view | * Maybe integration of administrative data (e.g. birthday, contact details) in an administrative view | ||
* Publications based on the pictures should be integrated in the application | |||
* Currently, there is no need for adding further pictures | * Currently, there is no need for adding further pictures | ||
* No possibility for changing the pictures | * No possibility for changing the pictures | ||
'''User Management''' | '''User Management''' | ||
| Line 88: | Line 84: | ||
'''Baskets''' | '''Baskets''' | ||
* The creation and storage of subsets from the collection for different user groups should be supported | * The creation and storage of subsets from the collection for different user groups should be supported | ||
'''Metadata''' | |||
* Development of a descriptive and a technical metadata set (maybe with a differentiation between individual-related and picture-related metadata) | |||
'''Quality Assurance''' | '''Quality Assurance''' | ||
| Line 97: | Line 96: | ||
=== Design === | === Technical Requirements === | ||
* Separation of the available metadata from the pictures (currently, the attributes are stored in the name of the pictures and the technical metadata directly in the JPAGs) | |||
=== Design Requirements === | |||
The application has to be branded with the following: | The application has to be branded with the following: | ||
* Name and logo of the institute | * Name and logo of the institute | ||
* | * Field of research or project level | ||
| Line 107: | Line 111: | ||
Currently, the MPI is working on a normstudy, for comparing their expert opinion about how an emotion have to look like with the opinion of layman. The results of this study, about 130 grouped values per picture, should be integrated in FACES. Approximately, this will not start before the end of 2008. | Currently, the MPI is working on a normstudy, for comparing their expert opinion about how an emotion have to look like with the opinion of layman. The results of this study, about 130 grouped values per picture, should be integrated in FACES. Approximately, this will not start before the end of 2008. | ||
This results are no further metadata for the pictures, but data. This data have to be connected to the pictures, but will be stored as separate items. | |||
| Line 118: | Line 124: | ||
== Project Documentation == | === Project Documentation === | ||
[[Category:ESciDoc]] | |||
Revision as of 11:42, 28 June 2007
NOTE: This page is currently under construction. Please don't edit it at the moment!
FACES is a collaboration of the MPDL with the Max Planck Institute for Human Development.
What is FACES[edit]
Overview[edit]
FACES is a lifespan database of adult emotional facial stimuli. It contains a set of images of naturalistic faces of 171 persons, separated in three different age groups (young, middle-aged and old) displaying each of 6 facial expressions: neutrality, sadness, disgust, fear, anger, and happiness.
For more information, please visit the FACES database homepage.
Details[edit]
Scope
- Developed between 2005-2007
- Currently 171 persons (men and women)
- 2 x 6 emotions
- 2052 pictures overall
- Available to defined user-group only as a java-application to be ordered by request on CD
Attributes
- ID, age group, gender, emotion, picture group
Emotions
- Neutrality, sadness, disgust, fear, anger, happiness
Age Groups
- Young (58 persons), middle-aged (56 persons), old (57 persons)
Picture Groups
- a and b (only as double check, no quality criteria)
Formats
- JPAG images
- Attribute export as CSV
Image Resolutions
- 819 x 1024
- 2835 x 3543
- Automatically generated thumbnails
What should FACES become[edit]
FACES should become an online open source solution, but with restricted access to the data because of the restricted usage rights for the photos.
Aim[edit]
Wesentlich wird es – neben der Einbindung in die eSciDoc-Architektur – darum gehen, die bisherigen "Attribute" auf der Ebene des einzelnen Bildes zu ergänzen um weitere, standardisierte Metadaten (ggf. METS) , und ein Rechtemanagement zu implementieren, d.h. differenzierte Zugriffsrechte zu ermöglichen. Dabei muss die Datenbank strukturell offen sein für die Aufnahme weiterer (Beschreibungs-) Daten – wie etwa von der Normierungsstudie zu erwarten (expressed by UF).
Functional Requirements[edit]
Browsing
- Browse photo collection
- View photos and their attributes
Searching
- Select photos according to their attributes (advanced search)
- Manually refine selection
Export
- Export result set including attribute data
Data Enrichment
- Adding of new attributes to images, also from external data via ingestion or one by one (new attributes have to be introduced to all images, also if the values are not available for all of them)
- Annotations of data sets (e.g blocking of a data set)
- Maybe integration of administrative data (e.g. birthday, contact details) in an administrative view
- Publications based on the pictures should be integrated in the application
- Currently, there is no need for adding further pictures
- No possibility for changing the pictures
User Management
- Visibility of the data only for registered users
- Online application form for an account
- Two different user roles: Reader and Editor
Baskets
- The creation and storage of subsets from the collection for different user groups should be supported
Metadata
- Development of a descriptive and a technical metadata set (maybe with a differentiation between individual-related and picture-related metadata)
Quality Assurance
- Currently, no quality assurance is necessary, because only a hand of people will get the Editor rights
- If later on, the group of Editors will be expanded to external scientists, the external data should be marked adequate (incl. a description of the used research method)
PID
- No PID (persistent identifier) for the individual photos is necessary, because the photos are not allowed to be cited, only the whole application
Technical Requirements[edit]
- Separation of the available metadata from the pictures (currently, the attributes are stored in the name of the pictures and the technical metadata directly in the JPAGs)
Design Requirements[edit]
The application has to be branded with the following:
- Name and logo of the institute
- Field of research or project level
Normstudy[edit]
Currently, the MPI is working on a normstudy, for comparing their expert opinion about how an emotion have to look like with the opinion of layman. The results of this study, about 130 grouped values per picture, should be integrated in FACES. Approximately, this will not start before the end of 2008.
This results are no further metadata for the pictures, but data. This data have to be connected to the pictures, but will be stored as separate items.
Project Management[edit]
Meetings[edit]
19.06.07 (Berlin): Kick off Meeting
08./09. oder 10.10.07 (Berlin): Follow up Meeting