Difference between revisions of "Imeji Scope"

From MPDLMediaWiki
Jump to navigation Jump to search
Line 95: Line 95:
*# on demand
*# on demand
*:: Possible Solution: to persist a collection and its items as one single item (instead of a container with many items): to be tested, might be even slower...
*:: Possible Solution: to persist a collection and its items as one single item (instead of a container with many items): to be tested, might be even slower...
* External content management (for instance images from other system than eSciDoc)
* Link imeji collection from Pubman
* Link imeji collection from Pubman
* Implementation of automatic tests
* Implementation of automatic tests
Line 102: Line 101:
* Link imeji with social services
* Link imeji with social services
* Subcollection (specs + implementation)
* Subcollection (specs + implementation)
* Print on demand for a collection or an album
* Use Icon Class (Need to find the API)
* Use Icon Class (Need to find the API)
* Desktop upload (upload images for one collection --> for each collection a imeji Desktop box has to be created)
* Desktop upload (upload images for one collection --> for each collection a imeji Desktop box has to be created)

Revision as of 06:46, 23 July 2013

Template:Imeji

Release 1.3.0.0[edit]

Time: tbd

Checkmark.png Release 1.2.0.0[edit]

Time: July 2013

Download: http://rd.mpdl.mpg.de/nexus/content/groups/public/org/imeji/imeji/1.2.0.0/imeji-1.2.0.0.war (md5: 6327fdd9dae4d10de00085ffead4f353)

Release 1.2.1.0[edit]

Time: July 2013

Checkmark.png Release 1.1.0.0[edit]

Time: April 2013

Download: http://rd.mpdl.mpg.de/nexus/content/groups/public/de/mpg/mpdl/imeji/imeji_ear/1.1.0.0/imeji_ear-1.1.0.0.ear (md5: eb4385d435c3b5f2b8a53da07266fd5e)

  • Update to JSF 2.0
  • Update jboss version/ tomcat support
  • Small gui changes (reported in git issues)
  • Decoupling of the css from the common presentation module
  • Start of css clean up
  • New functionalities
    • Choose the storage of imeji between internal and eSciDoc
    • Upload image by URL
    • Admin area: more information on db and storage
    • Admin area: advanced settings (beta)
    • Display of the MD checksum of an image
    • Export collections and albums in imeji format
    • XML export of the metadata profile of a collection
    • Homepage carousel configurable via properties file
    • Improved metadata profile handling: The order of the statements can be changed by drag&drop
    • Improved metadata profile handling (Beta): The metadata profile is now hierarchical

Checkmark.png Release 1.1.1.0[edit]

Time: April 2013

Download: http://rd.mpdl.mpg.de/nexus/content/groups/public/de/mpg/mpdl/imeji/imeji_presentation/1.1.0.1/imeji_presentation-1.1.0.1.war

  • This Release contains the same features as Release 1.1.0.0, plus the migration utility. If you want to use imeji 1.1.0.0 as upgrade from 1.0.0.0, please use this version and follow the migration instructions here: Imeji_migration .

Checkmark.png Release 1.1.2.0[edit]

Time: April 2013

Download: http://rd.mpdl.mpg.de/nexus/content/groups/public/de/mpg/mpdl/imeji/imeji_presentation/1.1.2.0/imeji_presentation-1.1.2.0.war

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/imeji_ear-1.0.0.0.ear (md5: 2b7253ad357db2542ad07381ac70c6ae)

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.

  • Export
    • As a tag cloud (via snippet and CSS?)
  • Metadata Editor: Implement possibility to set the obligation (mandatory/optional) of a metadata entry
  • Persist (analogue to PubMan)
    1. automatically when releasing:
      • Collection and pictures of the collection
      • Album
    2. on demand
    Possible Solution: to persist a collection and its items as one single item (instead of a container with many items): to be tested, might be even slower...
  • Link imeji collection from Pubman
  • Implementation of automatic tests
  • Media-RSS
  • Wordpress Plugin
  • Link imeji with social services
  • Subcollection (specs + implementation)
  • Use Icon Class (Need to find the API)
  • Desktop upload (upload images for one collection --> for each collection a imeji Desktop box has to be created)
  • Other data type management (non media): doc-files, Excel import with Mapping utility, etc.
    • Should we handle non media files in a media data repository? --Friederike 13:39, 26 March 2013 (CET)
  • Sort by metadata
  • User Groups: it would make sense to implement the creation of user groups, which than can have special user rights assigned similar to individual users.