Difference between revisions of "Imeji Functionalities"
Jump to navigation
Jump to search
(→Albums) |
|||
Line 37: | Line 37: | ||
# Create/edit collection (edit the metadata values) | # Create/edit collection (edit the metadata values) | ||
#* '''[Not implemented yet]''' For each collection, a individual style sheet (e.g. logo. color) can be defined | #* '''[Not implemented yet]''' For each collection, a individual style sheet (e.g. logo. color) can be defined | ||
# Delete/release/ | # Delete/release/discard collection | ||
# Display of collections | # Display of collections | ||
#* List of all published collections together with the most relevant metadata values | #* List of all published collections together with the most relevant metadata values |
Revision as of 14:16, 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]
|
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: