Difference between revisions of "Imeji Scope"
Jump to navigation
Jump to search
Kleinfercher (talk | contribs) m |
Kleinfercher (talk | contribs) |
||
Line 7: | Line 7: | ||
== Release 1.2.0.0 == | == Release 1.2.0.0 == | ||
Time: '''Summer 2013 | '''Time:''' Summer 2013 | ||
The imeji/HU/MMG release: | The imeji/HU/MMG release: |
Revision as of 10:25, 14 January 2013
Release 1.3.0.0[edit]
Time: End 2013
- Hyperimage integration
- ...?
Release 1.2.0.0[edit]
Time: Summer 2013
The imeji/HU/MMG release:
- Thesauri integration
- View collection in a map (with metadata information)
- Geo search
Release 1.1.0.0[edit]
Time: March 2013
The imeji GUI release:
- update to JSF 2.0
- Update jboss version
- Small gui changes (reported in git issues)
- xml import
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/
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.
Highest priority[edit]
- Export
- the pictures (collection, album, search)
- As a tag cloud (via snippet and CSS?)
- ldap integration
- imeji installer
- PID
- picture checksum
Lower priority[edit]
- Metadata Editor: Implement possibility to set the obligation (mandatory/optional) of a metadata entry
- Persist in eSciDoc (analogue to PubMan)
- automatically when releasing:
- Collection and pictures of the collection
- Album
- on demand
- Problem: Performance in eSciDoc (a Collection with 10.000 images needs about 330 minutes)
- 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...
- automatically when releasing:
- External content management (for instance images from other system than eSciDoc)
- Video data integration
- Sound data integration
- Link imeji collection from Pubman
- Implementation of automatic tests
- Media-RSS
- Wordpress Plugin
- Link imeji with social services
- Subcollection (specs + implementation)
- Excel import with Mapping utility
- Print on demand for a collection or an album
- Use geonames API
- Use Icon Class (Need to find the API)
- Collection homepage with themes
- Desktop upload (upload images for one collection --> for each collection a imeji Desktop box has to be created)
- Other data type management (non media): pdfs, words, etc.
- Integration of digilib (for zoom features)