Difference between revisions of "Imeji Functionalities"

Revision as of 06:40, 10 April 2012

This page gives a short overview of all imeji functionalities.
The detailed functional specifications can be found here.

Upload content

Creation of a collection with collection metadata
Assignment of a metadata profile to the collection
- via using an already defined profile as template
- via creating a new profile
Upload of pictures to the collection
- via selecting one or several single picture
- via selecting one zip file [Not implemented yet]
- via selecting one folder
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
Releasing the whole collection (make it visible for all users)

Definition
- A collection has exactly one metadata profile
- Every metadata profile is related to at least one collection (that means neither a collection nor a metadata profile can exist without the other)
- A collection has exactly one creator, but can have multiple 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)
Delete/release/discard collection
Display of collections
- List of all published collections together with the most relevant metadata values

Definition
- A metadata profile always belongs to a collection
- The user either can create a new metadata profile for a new collection or use an already available one as template.
Edit metadata profile
- Each metadata consists of
  - one type (a list with several types will be provided, e.g. date, geonames, string, integer, cone-person)
  - one or several labels
  - a language tag for each label
  - a menu to select cardinality (unique, multiple)
  - (optional) the possibility to define a small controlled vocabulary based on free text fields (strings)
Version control will not be provided for the metadata profile
- Therefore a metadata profile will be unique for each collection, no possibility to use it for more than one collection
- metadata profiles do not have an own release work flow as they inherit the collections work flow

Picture upload
1. Web upload (upload images for one collection)
  - via selecting one or several pictures
  - 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)
- 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


	Browse collections (collection portal: overview about all available collections) View images within one collection Filter images through facets based on the corresponding metadata profile Browse albums Browse images Filter images through general facets Navigate through images (paginator with additionally 'go to' functionality) View picture details


	Simple search: general free text search (any metadata value, either in images, collections, or [not implemented yet] albums) Advanced Search For pictures (metadata values) Select a collection and then a metadata element within this collection Combine as many collections and metadata elements as you want either with AND, OR, or NOT


	Creation and editing of private albums Adding pictures to an album via selecting one albums as 'active' album when browsing through the pictures Remove pictures from an album Deletion of a private album with all its content Publishing and discarding of an album


	Blog integration on the start page of imeji User management

@@ Line 54: / Line 54: @@
 # Edit metadata profile
 #* Each metadata consists of
-#** one type (a list with several types will be provided, e.g. date, geonames, string, integer, cone-person, tag)
+#** one type (a list with several types will be provided, e.g. date, geonames, string, integer, cone-person)
 #** one or several labels
 #** a language tag for each label
 #** a menu to select cardinality (unique, multiple)
 #** (optional) the possibility to define a small controlled vocabulary based on free text fields (strings)
-# Version control will not be provided for the MD profile
+# Version control will not be provided for the metadata profile
-#* Therefore a MD profile will be unique for each collection, no possibility to use it for more than one collection
+#* Therefore a metadata profile will be unique for each collection, no possibility to use it for more than one collection
-#* MD profiles do not have an own release workflow as they are always connected to one collection and its workflow
+#* metadata profiles do not have an own release work flow as they inherit the collections work flow
 |}