Difference between revisions of "Imeji Scope"

From MPDLMediaWiki
Jump to navigation Jump to search
(started clean up)
(clean up)
Line 15: Line 15:
A mingle-mangle of ideas which can be considered for next releases. <br/> Please put all bug reports directly in the [https://github.com/MPDL/Imeji/issues issue tracking system of github].
A mingle-mangle of ideas which can be considered for next releases. <br/> Please put all bug reports directly in the [https://github.com/MPDL/Imeji/issues issue tracking system of github].


== Next Steps ==
'''High Priority'''
* Persistieren in eSciDoc (analog zu PubMan)
* Persistieren in eSciDoc (analog zu PubMan)
*# automatisch bei dem Release von
*# automatisch bei dem Release von
Line 25: Line 22:
*: Problem: Performance in eSciDoc (eine Collection mit 10.000 Bildern braucht ca. 330 Minuten)
*: 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)  
*:: Lösung (evtl.):jede Collection nur als ein Item persistieren (nicht ein Item pro Bild)  
* OAI PMH Schnittstelle (einfachste technische Spezifikation
*: Folgende Objekte im Status released sollten auffindbar sein:
*:* Bilder
*:* Collections
*:* Alben
* RDF Export
* Google Sitemap
*: Folgende Metadaten sollten angezeigt werden:
*:* Collection: Titel + Autor
*:* Bilder: Titel (das Metadatum, das direkt unter dem Bild steht (bei der Thumbnail Ansicht))
*:* Album: Titel + Autor
* Jena refakturieren
* [http://jira.mpdl.mpg.de/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+IMEJI+AND+resolution+%3D+Unresolved+AND+fixVersion+is+EMPTY+ORDER+BY+priority+DESC&mode=hide Open Bugs] in Jira


'''Low Priority'''
* Use Case: Referenzieren von Bildern (Bilder liegen nicht in eSciDoc) --> wie könnte dieses Szenario aussehen?
* Use Case: Referenzieren von Bildern (Bilder liegen nicht in eSciDoc) --> wie könnte dieses Szenario aussehen?
* JSF 2.0
* JSF 2.0
Line 45: Line 28:
* Einbindung von Videos (ein Player für http Straem wird benötigt)
* Einbindung von Videos (ein Player für http Straem wird benötigt)
* Automatische Einbindung von Collections in PubMan --> wie könnte dieses Szenario aussehen?
* Automatische Einbindung von Collections in PubMan --> wie könnte dieses Szenario aussehen?
 
* imeji installer
== 1.0 ==
* Implementation of automatic tests
'''Features:'''
* Rework of help
* Internationalization (english and German First, then Japanese via NIMS) [[Image:Checkmark.png | 20px]]
* Images under-title self defined (via profile) [[Image:Checkmark.png | 20px]]
* CAN: Export (RDF, JSON?) [[Image:Symbol_Remove.png | 20px]]
 
'''Technical:'''
* Installer [[Image:Symbol_Remove.png | 20px]]
* Replacement of common logic by eSciDoc Java library [[Image:Symbol_Remove.png | 20px]]
* Replacement of JBoss by Tomcat as Application Server [[Image:Symbol_Remove.png | 20px]]
* CAN: Automatic tests (2 tests will be written for the beginning) [[Image:Symbol_Remove.png | 20px]]
 
'''GUI:'''
* CSS Bug: Waehtl man ein anderes als das schwarze CSS, werden die Overlays beim Hover ueber einzelne Bilder kaputt angezeigt (es fehlt der Hintergrund) [[Image:Checkmark.png | 20px]]
 
'''Functional:'''
* Rework of help [[Image:Checkmark.png | 20px]]
 
 
 
== R1 ==
 
The imeji run starting in January 2011!!!
 
'''Aim:'''
* To have a stable version (released on the [http://test-faces.mpdl.mpg.de/ FACES demo server]) which can be shown around
* To allow multiple users working on the same data
* To fix some bugs and some improvements
 
'''Tasks:'''
* Queue or Transactions for Jena updates (multiuser), see [http://jira.mpdl.mpg.de/browse/IMEJI-4 IMEJI-4]
* Re-engineer Jena Beans to be standard compliant
* Multiroot graph concept i.e. for collections or profile types
 
 
== Further Possible Improvements ==
 
Please list further possible improvements here, and '''NOT''' in Jira.
'''In Jira there should only be tasks already identified for the next run!!!'''
 
'''Technical'''
* Switch to JSF2
* Switch to GUI v3
* Cone Thesauri
* Cone Thesauri
** This would be coupled with a generic thesauri integration in Imeji (Define a new MD type, "thesaurus", working automatically with Cone.)
** This would be coupled with a generic thesauri integration in Imeji (Define a new MD type, "thesaurus", working automatically with Cone.)
* Plugin interface
* Media-RSS
* More multimedia types (i.e. video, audio,..), see [http://jira.mpdl.mpg.de/browse/IMEJI-14 IMEJI-14]
* Wordpress Plugin
* Login with escidoc Account
* Link Imeji with social services
** Downloaded images, collections, album, could be then easily available directly in Pubman (not via a link that refers to imeji), via a new workspace for instance.
* User geonames API
* Use Icon Class (Need to find the API)
* Import just references instead of files, see [http://jira.mpdl.mpg.de/browse/IMEJI-11 IMEJI-11]
* Improve handling of deleted images in escidoc
 
'''Functional'''
* Subcollection (specs + implementation)
* Subcollection (specs + implementation)
* Mass import (specs inspired from [http://batchgeo.com/ BatchGeo])
* Mass import (specs inspired from [http://batchgeo.com/ BatchGeo])
* Print on demand einer Collection / eines Albums
* Print on demand einer Collection / eines Albums
* Allow for multiple entries in one text area separated i.e. by comma (Use case: normal multiple tags) instead of multiple text areas
* User geonames API
* Adapt album handling to same behavior as collection handling (multiple selection, then add, instead of adding single images)
* Use Icon Class (Need to find the API)
* Allow users to define their own facets (e.g. Author=Mustermann, Author+Element (have a value))
* Pimp homepage
* Results from the usability evaluation (see [[Talk:Imeji_Backlog|Usability tests - feedback]])
* Collection homepage with themes


'''Graphical'''
* More list view types (text, columns)
* Collection homepage with themes
* Skinning (on collection level)
* Results from the usability evaluation (see [[Talk:Imeji_Backlog|Usability tests - feedback]])
* Pimp homepage (add more pictures, e.g. random like ViRR, smaller the news section as we see in other solution there are not much news!)


'''Add ons'''
* Wordpress Plugin
* Media-RSS, see [http://jira.mpdl.mpg.de/browse/IMEJI-13 IMEJI-13]
* Link Imeji with social services (Twitter, Facebook, etc.)


[[Category:Imeji|Backlog]]
[[Category:Imeji|Road Map]]

Revision as of 09:46, 4 April 2012

Template:Imeji

This is a protected page.

Release 0.1.0.0[edit]

The first stable release of imeji:

  • Jena update
  • Metadata export
  • OAI-PMH interface

Planned Releases[edit]

Here are all planned releases which do not have a version number now (not yet scheduled)

  1. GUI release

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.

  • 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?
  • JSF 2.0
  • Items über eine eindeutige ID ansteuern
  • Einbindung von Videos (ein Player für http Straem 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)
  • Pimp homepage
  • Results from the usability evaluation (see Usability tests - feedback)
  • Collection homepage with themes

Open Archives Initiative Protocol for Metadata Harvesting

Graphical User Interface

Enhanced Scientific Documentation

Publication Management

JavaServer Faces

Identifier

Metadata

Really Simple Syndication

Application Programming Interface

Retrieved from "https://colab.mpdl.mpg.de/mw010/index.php?title=Imeji_Scope&oldid=77535"