Difference between revisions of "Imeji Functionalities"
Jump to navigation
Jump to search
m (→Search) |
|||
Line 47: | Line 47: | ||
|- | |- | ||
! width="250" | | ! width="250" | | ||
| | |||
|- style="height:20px" | |- style="height:20px" | ||
| [[Image:Imeji_Metadata_Profile_klein.jpg|left|framed]] || | | [[Image:Imeji_Metadata_Profile_klein.jpg|left|framed]] || | ||
# | # 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 | |||
#* All metadata and its values are public | #* All metadata and its values are public | ||
#* Each metadata consists of | #* 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, tag) | ||
#** one label | #** one or several labels | ||
#** a language tag for each label | |||
#** a menu to select cardinality (unique, multiple) | #** a menu to select cardinality (unique, multiple) | ||
#** a menu to select the obligation (mandatory/optional) | #** '''[Not implemented yet]''' a menu to select the obligation (mandatory/optional) | ||
#** (optional) the possibility to define a small controlled vocabulary based on free text fields (strings) | #** (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 MD profile | ||
#* Therefore a MD profile will be unique for each collection, no possibility to use it for more than one collection | #* Therefore a MD profile will be unique for each collection, no possibility to use it for more than one collection | ||
#* MD | #* MD profiles do not have an own release workflow as they are always connected to one collection and its workflow | ||
|} | |} | ||
Revision as of 13:34, 27 September 2011
|
This page gives a short overview of all Imeji solution functionalities.
The detailed functional Specifications can be found here.
Standard User Workflow[edit]
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
- 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)
Collection Management[edit]
|
Metadata Profile Management[edit]
|
Upload[edit]
Data ingest by the user
|
Metadata Editing[edit]
|
Browsing[edit]
|
Search[edit]
|
Albums[edit]
|
Further Features[edit]
|
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!
- Keep in mind that there are two different use cases possible: