Imeji Scope
|
This is a protected page.
Run Planing[edit]
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:
- Rework of help
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]
Not planned[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
- Cone Thesauri
- Geonames
- 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)
- Translation of metadata profiles in other languages, see IMEJI-6
- 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 - feeback)
Add ons
- Wordpress Plugin
- Media-RSS, see IMEJI-13
- Link Imeji with socail services (Twitter, Facebook, etc.)
Basic Meta Data[edit]
- I'd strongly vote for having Basic MD (for all images) + Specific MD (collection-specific) --Rupert 11:11, 15 July 2010 (UTC)
- What about having title, description, dates (created, modified etc. - created for start would be sufficient), subject (keywords), creator - as in PubMan (person or organization - in latter case could be even an instrument e.g. microscope) as common metadata?
- That would be fine. --Rupert 15:16, 27 July 2010 (UTC)
- Currently in Faces (and also in Diamonds) we do not have description. Further on, subjects are to general (we want to make customizable metadata sets) and date modified is very raw when working with pictures. The metadata I am fine with is title (filename) and date created (therewith I mean the date when the picture was actually taken). Further on, we also could use date uploaded (when the picture was uploaded into the system). --Kristina 06:53, 28 July 2010 (UTC)