Difference between revisions of "Imeji Functionalities"
Jump to navigation
Jump to search
m |
|||
| Line 36: | Line 36: | ||
#* A collection has one entry point | #* A collection has one entry point | ||
# 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 | ||
# Delete/release/withdraw collection | # Delete/release/withdraw collection | ||
# Display of collections | # Display of collections | ||
| Line 79: | Line 79: | ||
#* via selecting a zip | #* via selecting a zip | ||
#* via selecting one or several pictures | #* 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 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 | #** upload pictures to the local Imeji DropBox and later to Imeji repository | ||
| Line 86: | Line 86: | ||
# Extract technical metadata (IPTC [http://en.wikipedia.org/wiki/IPTC_Information_Interchange_Model]) | # Extract technical metadata (IPTC [http://en.wikipedia.org/wiki/IPTC_Information_Interchange_Model]) | ||
#* Technical md will be displayed only in xml (via link) | #* 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 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 | #* Define parsing: which value should be mapped to which metadata from the schema | ||
#* Update items with populated md-record | #* 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 | ||
|} | |} | ||
| Line 146: | Line 146: | ||
#* 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. | #* 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 | # Advanced Search | ||
## ''' | ## '''[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 | ||
## ''' | ## '''[Not implemented yet]''' For albums (album metadata) | ||
## For pictures (metadata values) | ## For pictures (metadata values) | ||
##* Select a metadata set or a collection | ##* Select a metadata set or a collection | ||
Revision as of 13:37, 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: