Talk:Imeji

if upload "via selecting a folder" isn't going to be supported by a desktop application (as opposed to a web application), i don't see how this could be done. not even the flickr uploader - probably a pretty elaborate/polished one - works without quirks (e.g. it doesn't work for me at home over dsl).--Robert 08:43, 7 May 2010 (UTC)

• it would be good to distinguish clearly the terms of image-level metadata profile and collection-level metadata profile.
• in faces 4.0 still all collections will have 1 single metadata profile - that is at present publication metadata profile.
• images may have different metadata profiles in Faces - however - only 1 image-profile can be defined for all images within a collection.
• albums - as they can aggregate images from various collections - image-level profiles are actually dependent on the profiles of *images they aggregate --Natasa 15:22, 10 May 2010 (UTC)

• to check if there are data model changes needed - additionally to what is offered

Upload

• Single file or ZIP upload can be done seamless by recognizing the MIME-type or the extention.
• Folder is impossible by browser
• Multi file upload requires JQuery extension, techically possible but depends on GUI Dev

--Rupert 11:09, 15 July 2010 (UTC)

Meta Data

• I'd strongly vote for having Basic MD (for all images) + Specific MD (collection-specific)

--Rupert 11:11, 15 July 2010 (UTC)

What about having title, description, dates (created, modified etc. - created for start would be sufficient), subject (keywords), creator - as in PubMan (person or organization - in latter case could be even an instrument e.g. microscope) as common metadata?

Conventions

• Metadata profile or metadata set is used to describe the concrete metadata set used by a collection for description of the collection images

• Namespaces are used to describe collections of URIs assigned to properties, classes and encoding schemes.
  • Would reccomend to use glossary similar to DCMI-Namespace Glossary
  • Translated, the following glossary could be used (note: eSciDoc we can replace with MPDL or anything else):

• term

   A property (element), class, vocabulary encoding scheme, or syntax encoding scheme.

• URI

   A Uniform Resource Identifier [URI] or Internationalized Resource Identifier [IRI].

• eSciDoc term URI

   The URI that identifies a term.

• term name

   A unique token assigned to a term (e.g. for all DCMI terms, the term name is appended to a DCMI namespace URI to create the *eSciDoc term URI
   The URI for a term that is declared and managed by eSciDoc.

• term label

   A human-readable label assigned to a term.

• eSciDoc namespace

   A collection of eSciDoc term URIs where each term is assigned a URI that starts with the same 'base URI'. The 'base URI' is known as the eSciDoc namespace URI. (Note that an eSciDoc namespace is not the same as an 'XML namespace').

• eSciDoc namespace URI

   The URI that identifies a DCMI namespace.

• eSciDoc term declaration

   machine-processable representation of one or more eSciDoc terms, expressed in a schema language (RDFS, XSD).

• metadata record - contains descriptions (description sets) about one or more resources e.g. image and an author
• desctription (set)

Note that the Metadata profiles can use terms from several namespaces (not only eSciDoc namespace, e.g. dc, dcterms, kml etc.)

Coordinated Universal Time

Multipurpose Internet Mail Extensions

Graphical User Interface

Metadata

Publication Management

Enhanced Scientific Documentation

Max Planck Digital Library

Uniform Resource Identifier

Dublin Core Metadata Initiative

Extensible Markup Language

XML Schema Definition