Difference between revisions of "Imeji Scope"
Jump to navigation
Jump to search
Line 97: | Line 97: | ||
'''Technical''' | '''Technical''' | ||
* Switch to JSF2 | * 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.) |
Revision as of 10:58, 2 December 2011
|
This is a protected page.
Further Planing[edit]
Next Steps[edit]
High Priority
- 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: 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)
- automatisch bei dem Release von
- OAI PMH Schnittstelle (einfachste technische Spezifikation
- Folgende Objekte im Status released sollten auffindbar sein:
- Bilder
- Collections
- Alben
- Folgende Objekte im Status released sollten auffindbar sein:
- 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
- Folgende Metadaten sollten angezeigt werden:
- Jena refakturieren
- Open Bugs in Jira
Low Priority
- 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?
1.0[edit]
Features:
- Internationalization (english and German First, then Japanese via NIMS)
- Images under-title self defined (via profile)
- CAN: Export (RDF, JSON?)
Technical:
- Installer
- Replacement of common logic by eSciDoc Java library
- Replacement of JBoss by Tomcat as Application Server
- CAN: Automatic tests (2 tests will be written for the beginning)
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)
Functional:
Timeshedule[edit]
01.08. - 09.09.: | Development (incl. 2 weeks vacation) |
31.08.: | Send resource bundles to Masao for Japanese translation |
12.09. - 16.09.: | Development tests |
19.09. - 27.09.: | Functional testing + Bug fixing |
28.09. - 29.09.: | Final testing |
30.09.: | Release |
R1[edit]
The imeji run starting in January 2011!!!
Aim:
- To have a stable version (released on the 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 IMEJI-4
- Re-engineer Jena Beans to be standard compliant
- Multiroot graph concept i.e. for collections or profile types
Further Possible Improvements[edit]
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
- This would be coupled with a generic thesauri integration in Imeji (Define a new MD type, "thesaurus", working automatically with Cone.)
- Plugin interface
- More multimedia types (i.e. video, audio,..), see IMEJI-14
- Login with escidoc Account
- 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 IMEJI-11
- Improve handling of deleted images in escidoc
Functional
- Subcollection (specs + implementation)
- Mass import (specs inspired from BatchGeo)
- 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
- Adapt album handling to same behavior as collection handling (multiple selection, then add, instead of adding single images)
- Allow users to define their own facets (e.g. Author=Mustermann, Author+Element (have a value))
Graphical
- More list view types (text, columns)
- Collection homepage with themes
- Skinning (on collection level)
- Results from the usability evaluation (see Usability tests - feedback)
Add ons
- Wordpress Plugin
- Media-RSS, see IMEJI-13
- Link Imeji with social services (Twitter, Facebook, etc.)