|
|
| (72 intermediate revisions by 7 users not shown) |
| Line 1: |
Line 1: |
| {{Faces}} | | {{Imeji_Tech}} |
|
| |
|
| The FACES Release 4.0 will bring a lot new functionality to FACES as now the user should be able to create his own collections. This page should help us to make the functionalities of the new release more clearly.
| |
|
| |
|
| == General Definitions == | | == imeji - Publish Your Scientific Multimedia Data == |
| * '''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
| |
|
| |
|
| == User Roles == | | <font color=#6CAD2F>'''imeji creates citable research assets by describing, enriching, sharing, exposing, linking and archiving data.''' </font> |
|
| |
|
| {| border="1"
| | '''For information about the imeji software and the imeji community please visit [http://imeji.org imeji.org] ''' |
| |width="170pt" align="center"| '''Label'''
| |
| |width="550pt" align="center"| '''Description'''
| |
| |width="250pt" align="center"| '''eSciDoc Role'''
| |
| |-
| |
| | '''Account User'''
| |
| |
| |
| * create collection(s)
| |
| * '''inherits all rights from the Collection Administrator'''
| |
| | (context: whole imeji)
| |
| |-
| |
| | '''Collection Administrator'''
| |
| |
| |
| Is allowed to work on one specified collection (context)
| |
| * define collection administrators, collection editors and picture editors for the collection
| |
| * '''inherits all rights from the Collection Editor'''
| |
| | (context: only one specific collection)
| |
| |-
| |
| | '''Collection Editor'''
| |
| |
| |
| Is allowed to work on one specified collection (context)
| |
| * edit collection and metadata profile of the collection
| |
| * release/withdraw collection
| |
| * '''inherits all rights from the Picture Editor'''
| |
| | (context: only one specific collection)
| |
| |-
| |
| | '''Picture Editor'''
| |
| |
| |
| Is allowed to work on pictures of one specified collection (context)
| |
| * upload pictures
| |
| * assign metadata values
| |
| * '''inherits all rights from the Collection Viewer'''
| |
| | (context: only one specific collection)
| |
| |-
| |
| | '''Collection Viewer'''
| |
| | Is allowed to view private pictures of a released collection (context)
| |
| | (context: only one specific collection)
| |
| |}
| |
|
| |
|
| == Functionalities ==
| |
|
| |
|
| === [[Faces_Metadata#Metadata_Profile|Metadata Profile Management]] ===
| |
| # 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
| |
| #* It is only possible to delete the whole metadata profile or to extend it (add new metadata values)
| |
|
| |
|
| === [[Faces_Collection_Management|Collection Management]] ===
| |
| # Definition
| |
| #* A Collection has exactly one md profile
| |
| #* The relation between collection and MPD 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 with one md profile and a default style sheet (e.g. logo. color)
| |
| #* For each collection, a individual style sheet can be defined
| |
| # Collection metadata profile
| |
| #* A collection has a publication md profile with additional information about the style sheet
| |
| #* Edit collection (edit the metadata values)
| |
| # Delete/release/withdraw collection
| |
|
| |
|
| === [[Faces_Pictures|Upload]] ===
| | [[Category:Imeji|imeji Software ]] |
| Data ingest by the user
| |
| # Web upload (upload images for one collection)
| |
| #* via selecting a zip
| |
| #* via selecting one or several pictures
| |
| # Desktop upload (upload images for one collection --> for each collection a Faces Desktop box has to be created)
| |
| #* Upload all images dragged and dropped into Faces Desktop box (a file scan during upload will not be possible for this sort of upload)
| |
| #** upload pictures to the local Faces DropBox and later to Faces repository
| |
| #** inform the user when the images are uploaded Faces 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 [http://en.wikipedia.org/wiki/IPTC_Information_Interchange_Model])
| |
| #* Technical md will be displayed only in xml (via link) like in the current implementation
| |
| # Scan filename (this can be part of the web upload or triggered separately after the upload)
| |
| #* Define pattern via analysing 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
| |
| # Define visibility, only possible for the whole import, not for individual pictures; but can be changed later manually for each picture
| |
| | |
| === [[Faces_Metadata#Metadata_Values|Metadata Editing]] ===
| |
| # 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). 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!
| |
| # Edit metadata of a single image (is same a batch editing with only one image selected)
| |
| | |
| === Browsing ===
| |
| # 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 --> now sorting is nice)
| |
| | |
| === Search ===
| |
| # Simple search: general free text search (any metadata value, either in collection, album or image)
| |
| #* To make it technically easier, it should not happen that images, collections and albums will be displayed in one search result list. That means when such an search list would occur, the user first has to decide whether he wants to see the results in the images, collections or albums (or we just use images as default and offer the other two as optional).
| |
| # Search 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
| |
| # Search for albums (album metadata)
| |
| # Search for pictures (metadata values)
| |
| #* Select a metadata set or a collection
| |
| #* Do advanced search for the selected metadata set or the collection
| |
| | |
| === 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
| |
| | |
| === Further Functionalities ===
| |
| * Researchers homepage (Wordpress plugin)
| |
| * Surrogate item implementation
| |
| | |
| == User Workflow ==
| |
| | |
| '''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)
| |
| | |
| == Scenarios ==
| |
| | |
| To get a more precise shape of the amount/complexity of data. One assumption would be the upload of pictures from a field trip (zoology):<br>
| |
| '''1. Initial collection size (Images from Import)''' <br>
| |
| < 5000
| |
| | |
| '''2. MD profile example'''<br>
| |
| Basic Meta Data?
| |
| *Date: Date
| |
| *Owner: ConE
| |
| *Image Format: String
| |
| *Imaging Device: String
| |
| | |
| Collection Specific Meta Data?
| |
| *Import Date: Date
| |
| *Author: ConE, String
| |
| *Collection Type: Project, Excursion, Archive
| |
| *Gender: Male, Female, not known
| |
| *Habitat: Multiplicity
| |
| *Coutry: Coutry Code ISO 3166
| |
| *GeoLocation: String
| |
| *Migration: Yes, No
| |
| *Age: Adult, Juvenile
| |
| *Temperature: Number
| |
| | |
| '''3. Collaboration'''
| |
| *Scientist who imports and does classification
| |
| | |
| === Search/Edit MD Examples ===
| |
| | |
| Within the given meta data search and browse examples could to be tackled at the GUI:<br>
| |
| '''Example 1'''
| |
| #Find a picture set where author is Miller, location is Argentinia and Specie has not been set. Pictures should have been taken before 12.05.2009
| |
| #The set needs to be browsed
| |
| #All pictures of this set should get specie "Locustella naevia"
| |
| | |
| '''Example 2'''
| |
| Author and location of the pictures where temperature is below -10° Celsius should be set to Location:Canada, Author:Huber.
| |
| | |
| '''Example 3'''
| |
| Meta Data of pictures, where specie has not been set and author is not Dr. Engelmann, should be edited one by one.
| |
| | |
| | |
| [[Category:Imeji| ]] | |
