Imeji Scope

From MPDLMediaWiki
Revision as of 15:57, 30 October 2012 by Kleinfercher (talk | contribs) (→‎Release 1.1.0.0: added new release)
Jump to navigation Jump to search

Template:Imeji


Release 1.2.0.0[edit]

Time: TBD

  • xml import


Release 1.1.0.0[edit]

Time: TBD

The imeji GUI release:

  • update to JSF 2.0
  • Update jboss version
  • Small gui changes (reported in git issues)

Checkmark.png Release 1.0.0.0[edit]

Time: October 2012

Download: http://rd.mpdl.mpg.de/nexus/content/groups/public/de/mpg/mpdl/imeji/imeji_ear/1.0.0.0/

The first stable release of imeji:

  • Jena refactoring
  • Metadata export
  • OAI-PMH interface
  • Metadata Standards
  • New functionality: automatic sitemap generation
  • Code clean up and bugfixes
  • Rework of startpage
  • Integration of Google Geo API
  • Display and revise of search query
  • Improved advanced search (exact query, negation)


Possible Features, Improvements etc.[edit]

A mingle-mangle of ideas which can be considered for next releases.
Please put all bug reports directly in the issue tracking system of github.


  • Metadata Editor: Implement possibility to set the obligation (mandatory/optional) of a metadata entry
  • Persistieren in eSciDoc (analog zu PubMan)
    1. automatisch bei dem Release von
      • Collections
      • Albums: da ein Nutzer nicht unbedingt alle Rechte für alle Bilder innerhalb eines Albums hat, kann er die Bilder im Album nicht persistieren, nur das Album an sich (die Metadaten + die Referenzen zu den Bildern)
    2. per Knopfdruck
    Problem: Performance in eSciDoc (eine Collection mit 10.000 Bildern braucht ca. 330 Minuten)
    Lösung (evtl.):jede Collection nur als ein Item persistieren (nicht ein Item pro Bild)
  • Use Case: Referenzieren von Bildern (Bilder liegen nicht in eSciDoc) --> wie könnte dieses Szenario aussehen?
  • Items über eine eindeutige ID ansteuern
  • Einbindung von Videos (ein Player für http Stream wird benötigt)
  • Automatische Einbindung von Collections in PubMan --> wie könnte dieses Szenario aussehen?
  • imeji installer
  • Implementation of automatic tests
  • Rework of help
  • Cone Thesauri
    • This would be coupled with a generic thesauri integration in imeji (Define a new MD type, "thesaurus", working automatically with Cone.)
  • Media-RSS
  • Wordpress Plugin
  • Link imeji with social services
  • Subcollection (specs + implementation)
  • Mass import (specs inspired from BatchGeo)
  • Print on demand einer Collection / eines Albums
  • User geonames API
  • Use Icon Class (Need to find the API)
  • Results from the usability evaluation (see Usability tests - feedback)
  • Collection homepage with themes
  • Desktop upload (upload images for one collection --> for each collection a imeji Desktop box has to be created)
  • Export
    • the pictures (collection, album, search)
    • As a tag cloud (via snippet and CSS?)