Difference between revisions of "Imeji Scope"

From MPDLMediaWiki
Jump to navigation Jump to search
m (fixed broken link)
 
(114 intermediate revisions by 5 users not shown)
Line 1: Line 1:
{{Imeji}}
'''Please note:''' Content was moved to http://imeji.org/development/scope/


== Release 1.0.0.0 ==
Time: '''Sept. 2012'''


The first stable release of imeji:
[[Category:Imeji_Content_moved|Scope]]
* Jena refactoring
* Metadata export
* [http://colab.mpdl.mpg.de/mediawiki/Imeji_Interfaces OAI-PMH interface]
* [http://colab.mpdl.mpg.de/mediawiki/Category:Imeji_terms Metadata Standards]
* [[Code clean up|Code clean up]]
 
== Planned Releases ==
Here are all planned releases which do not have a [http://colab.mpdl.mpg.de/mediawiki/Imeji_Versioning version number] now (not yet scheduled).
# GUI release
 
== Possible Features, Improvements etc. ==
A mingle-mangle of ideas which can be considered for next releases. <br/> Please put all bug reports directly in the [https://github.com/imeji-community/imeji/issues 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)
*# 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)
*# per Knopfdruck
*: Problem: [[Imeji_Metadata_Update|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?
* JSF 2.0
* 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 [http://batchgeo.com/ BatchGeo])
* Print on demand einer Collection / eines Albums
* User geonames API
* Use Icon Class (Need to find the API)
* Improve homepage
* Results from the usability evaluation (see [[Talk:Imeji_Backlog|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 of an album
 
 
[[Category:Imeji|Road Map]]

Latest revision as of 12:52, 6 February 2014

Please note: Content was moved to http://imeji.org/development/scope/