Imeji

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 FACES Release 4.0 will bring a lot new functionality to FACES as now the user should be able to create his own collections. This page should help us to make the functionalities of the new release more clearly.

General Definitions

• Collection: has exactly one collection-level metadata profile, and specific image-level metadata profile. It can happen that image-level metadata profiles are used in several collections
• Album: can contain pictures from several collections --> images within an album could have different metadata profiles

Scenarios

To get a more precise shape of the amount/complexity of data. One assumption would be the upload of pictures from a field trip (zoology):

1. Initial collection size (Images from Import)

< 5000

2. MD profile example

Basic Meta Data?

• Date: Date
• Owner: ConE
• Image Format: String
• Imaging Device: String

Collection Specific Meta Data?

• Import Date: Date
• Author: ConE, String
• Collection Type: Project, Excursion, Archive
• Gender: Male, Female, not known
• Habitat: Multiplicity
• Coutry: Coutry Code ISO 3166
• GeoLocation: String
• Migration: Yes, No
• Age: Adult, Juvenile
• Temperature: Number

3. Collaboration

• Scientist who imports and does classification

Search/Edit MD Examples

Within the given meta data search and browse examples could to be tackled at the GUI:

Example 1:

1. Find a picture set where author is Miller, location is Argentinia and Specie has not been set. Pictures should have been taken before 12.05.2009
2. The set needs to be browsed
3. All pictures of this set should get specie "Locustella naevia"

Example 2:

Author and location of the pictures where temperature is below -10° Celsius should be set to Location:Canada, Author:Huber.

Example 3:

Meta Data of pictures, where specie has not been set and author is not Dr. Engelmann, should be edited one by one.

Functionalities

Metadata Profile Management

1. Create/edit simple metadata profile (each metadata consists of one type and one label)
   • Metadata profile must be under version control, with a pending+publish life cycle. When creating a new version (V2), this version will not automatically be updated for all collections that are using the old version (V1). But in a separate step, the user should have the possibility to adopt V2 to a collection that was using V1. This is only possible for collections the user is the owner of. Because when V2 consists of less metadata than V1, it could happen that some metadata values will be deleted. That means that automatically a new version of all the items (pictures) within the collection will be created.

   New scenario: some md should be private, some public. How can we handle that? (Bastien will take care of this topic.)

   • Use metadata types from a list provided by the MPDL (e.g. geonames, date, cone-person, string, integer)
   • Define labels for a metadata
   • Add/remove metadata
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/edit collection with one md profile and a default style sheet (e.g. logo. colour)

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

2. Edit collection metadata (the collection metadata profile will consist of the publication metadata profile (similar to an album) and a specific metadata profile for the style sheet information.

Upload

Data ingest by the user

1. Web upload (upload images for one collection)
   • via selecting a folder
   • via selecting a zip
   • via selecting one or several pictures
2. Desktop upload (upload images for one collection --> for each collection a Faces Desktop box has to be created)
   • Upload all images dragged and dropped into Faces Desktop box (a file scan during upload will not be possible for this sort of upload)
     • as researcher I would like to upload my pictures from the camera to the ( local Faces DropBox and later to) Faces repository
     • as researcher I would like to drag/drop the directory where the images from my last research (August, 2009, excavation site S1) reside to the (local Faces DropBox and later to) Faces repository
     • as researcher I would like to be informed when the images are uploaded to the (local Faces DropBox and later to) Faces repository via email and have a link to the list of last uploaded images via which I can directly access and continue my work
     • as researcher I would like to have the upload report about success/failures/reasons of failed uploads
     • as researcher I would like to export selected images from my Flickr account to the Faces repository

       what happens when users upload something else then an image? (who takes care of it, is it the uploading service that validates only, or additionally desktop upload?

3. Create thumbnails and web resolution and upload all 3 resolutions
4. Extract technical metadata (IPTC [1])
5. Create items with technical metadata (filename, size, ...) but empty metadata record
6. Scan filename (this can be part of the web upload or triggered separately after the upload)
   • Define pattern via analysing one selected filename: how are the different md values in the filename separated (e.g. via ",")
   • Define parsing: which value should be mapped to which metadata from the schema
   • Update items with populated md-record
7. Import workspace (= concept behind the import: is the user allowed to start several imports in parallel? Can he work with Faces while the import is executed?) --> Similar to PubMan

Metadata Editing

1. Batch editing
   • Filter/sort/search the images based on already available metadata values (e.g. technical metadata: date creation, already populated values)
   • Select images (via multiple click, batch select)
   • Edit metadata values (retrieved from related schema) of selected images from edit mask (metadata are stored in item metadata record). Keep in mind that there are two different use cases possible:
     • if edit can be done under a couple of seconds without any errors (preferred way)
     • if not, should certainly be specified something like an edit workspace where a report can be displayed etc. (not so nice)

   --> depends on the results of the dev team demonstrators!

2. Edit metadata of a single image (is same a batch editing with only one image selected)
3. Metadata workspace to enable asynchronous editing

Browsing

1. Browse by collection (collection portal: overview about all available collections)
   • Browse pictures within one collection (sorting by the md set)
2. Browse by albums
   • Browse pictures within one album
     • Sorting, when the pictures within one album use different metadata profiles: all md values are available in the drop down menu. Images which don't have any value for MD1 will then be sorted at the end of the MD1 list based on the default eSciDoc sorting criteria (probably eSciDoc ID).
   • Filter within the album (e.g. by metadata profile --> now sorting is nice)

Search

1. General free text search (any metadata value, either in album, picture or collection)
   • To make it technically easier, it should not happen that images, collections and albums will be displayed in one search result list. That means when such an search list would occur, the user first has to decide whether he wants to see the results in the images, collections or albums (or we just use images as default and offer the other two as optional).
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 or a collection
   • Do advanced search for the selected metadata set or the collection

Versioning

1. View older versions of an item (the picture together with its metadata)
2. View older versions of a metadata profile

Further Functionalities

• Researchers homepage (Wordpress plugin)
• Surrogate item implementation

User Workflow

Upload content

1. Creation of a collection with collection metadata
2. Assignment of a metadata profile to the collection
   • via using an already defined profile (It was decided that a profile can not be reused (one profile related to many collections). It is only possible to use an existing profile as kind of a template to create a new one.--Friederike 15:07, 15 June 2010 (UTC))
   • via creating a new profile
3. Upload of pictures to the collection
   • via selecting one or several single picture
   • via selecting one zip file
   • via selecting one folder
4. Assignment of metadata to pictures
   • Automatic extraction and assignment of technical metadata
   • Defining of a picture set for batch editing of descriptive metadata via filtering and sorting mechanism
   • Editing of the descriptive metadata of a single picture
5. Releasing the whole collection (make it visible for all users)

The user can additionally decide to version this release (permlink scenario).--Friederike 15:09, 15 June 2010 (UTC)

Metadata

International Organization for Standardization

Graphical User Interface

Max Planck Digital Library

Coordinated Universal Time

International Press Telecommunications Council

Publication Management

Enhanced Scientific Documentation

Identifier