Imeji Functionalities

	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

About[edit]

Imeji is the successor of the software used for the FACES and the DIAMONDS projects.

With Imeji, users can create own image collections and albums. For each collection, a metadata profile can be defined to describe the characteristics of the images within by using texts, numbers, controlled vocabularies, dates, locations, or URIs, giving all metadata elements own labels. This enables complex queries and faceted display of search results. Imeji allows an easy and efficient upload of images through the web browser. Metadata can be edited comfortably for single or multiple images, allowing also efficient maintenance of larger image sets. Subsets of images can be created as albums for re-use in publications. Albums offer stable citations of the subset after released to public.

This page gives a short overview of all Imeji solution functionalities. For further support, please check our support page.
The detailed functional Specifications can be found here.

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

Metadata Profile Management[edit]

Create/edit simple metadata profile
- All metadata and its values are public
- Each metadata consists of
  - one type (a list with several types will be provided, e.g. date, geonames, string, integer, cone-person, tag)
  - one label (either defined by the user himself or chosen out of an list of already existing metadata)
  - a menu to select cardinality (unique, multiple)
  - a menu to select the obligation (mandatory/optional)
  - (optional) the possibility to define a small controlled vocabulary based on free text fields (strings)
- It is possible to use an existing MD profile of another collection as template
Version control will not be provided for the MD profile
- Therefore a MD profile will be unique for each collection, no possibility to use it for more than one collection
- MD profile will not be active released: only the actions save, modify and delete are possible
  - saved: the MP profile is visible for other users (technically published)
- All profiles are public visible

Collection Management[edit]

Definition
- A Collection has exactly one md profile
- The relation between collection and md profile is 1-1 (that means neither a collection nor a md profile can exist without the other)
- A Collection has exactly one creator, but can have more editors (people who are allowed to assign metadata values and upload pictures) --> the creator automatically has the editor role for his collection
- A collection has one entry point
Create/edit collection (edit the metadata values)
- (Not implemented yet) For each collection, a individual style sheet (e.g. logo. color) can be defined
Delete/release/withdraw collection
Display of collections
- List of all published collections together with the most relevant metadata values

Upload[edit]

Data ingest by the user

Web upload (upload images for one collection)
- via selecting a zip
- via selecting one or several pictures
(Not implemented yet) Desktop upload (upload images for one collection --> for each collection a Imeji Desktop box has to be created)
- Upload all images dragged and dropped into Imeji Desktop box (a file scan during upload will not be possible for this sort of upload)
  - upload pictures to the local Imeji DropBox and later to Imeji repository
  - inform the user when the images are uploaded Imeji repository together with a report (will be within the ingest workspace)
Create thumbnails and web resolution and upload all 3 resolutions
Extract technical metadata (IPTC [1])
- Technical md will be displayed only in xml (via link)
(Not implemented yet) Scan filename (this can be part of the web upload or triggered separately after the upload)
- Define pattern via analyzing 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
(Not implemented yet) Define visibility, only possible for the whole import, not for individual pictures; but can be changed later manually for each picture

Metadata Editing[edit]

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)
Edit metadata of a single image (is same a batch editing with only one image selected)

Browsing[edit]

Browse by collection (collection portal: overview about all available collections)
- Browse pictures within one collection (sorting by the md set)
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)
Selecting
- Select images
- View selected images
General browsing functionalities
- Customizable 'hits per page'
- Multiple sorting
- Browse images
  1. by navigating through metadata facets
  2. by navigating through images (paginator with additionally 'go to' functionality)
  3. by using different filter options
- View picture details

Search[edit]

Simple search: general free text search (any metadata value, either in collection, album or image)
- To make it technically easier, it does not happen that images, collections and albums will be displayed in one search result list. Therefore the user first has to decide whether he wants to search for images (default) or collections and albums.
Advanced Search
1. (Not implemented yet) For collections (e.g. which collection has a metadata field called temperature); evtl. some lists will be offered to the user to choose between the available metadata labels
2. (Not implemented yet) For albums (album metadata)
3. For pictures (metadata values)
  - Select a metadata set or a collection
  - Do advanced search for the selected metadata set or the collection

Albums[edit]


	Creation and editing of private albums Adding pictures to an album via selecting one albums as 'active' album Remove pictures from an album Editing of album metadata Deletion of a private album with all its content Publishing and withdrawing of an album Export the pictures of an album

Further Features[edit]


	Researchers homepage (Wordpress plugin) Surrogate item implementation User management

Outlook[edit]

Versioning
- General, no versioning will be provided
- One exception:
- Permlink scenario: the user wants to cite the current state of the collection --> he can create a version with a citable URL

Edit metadata values
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!