1.0 Beta release 30 Jan

• Basic Backend
• SWikyNotes Integration.
• Basic OAI
• Manual and tutorial

Generic Talia 1.0

Most Important

• Incremental Publication #1107, #1108, #1117, #1120
• Optimisation #1126, #1127 (Try an HTTP cache in Apache?)
• "Generic Import ( Import arbitrary "source types" and "relations") #1107
• Import/show/browse EAD #1131 and Images from Ariannaweb and eGallery/Divenire #1132 (see for example this, this and this) #1136, #1137, #1138.
• Sysadmin manual and Administrator manual #1139 Tutorial #1153
• Installation scripts should be available for Talia (not for discovery as of now) #1145
• In the import and user interface handle "collections" as "discovery:editions" minus the weird naming thing. There should be a default "belongs_to_collection" property. The backend should allow users to assing a source to one or more collections and to create new collections (that have a name, creation date, description).
• Backend file upload. #1154
• Make a base data structure, check if the Fedora/DuraSpace ontology may be used as a base for the standard classes.
• New name - a logo - a website
• Implement a TaliaCore::Collection class, which works almost like TaliaCore::Catalog does now - it will also have some handy methods of course

SWikyNotes(Philospace) & Talia

• Ontology hosting #1141, #1144
• THCTags #1142

Important (should be included in 1.0)

• Comply with Linked Data ( http://www4.wiwiss.fu-berlin.de/bizer/pub/LinkedDataTutorial/ ) see #1151
• Authoritative annotations (especially source-source relations) generated from philospace and immediately shown on the web.
  • Import philospace rdf data in a context
  • show them in a nice and easy way
• Fix the ugly admin interface.
  • add "lost your password"?
  • Further user management (roles, etc.)
  • As of now it seems it is impossible to delete a user
  • Modify string properties on Sources in the backend
• Fix OAI-PMH (mapping of generic properties in the import file to unqualified DC). We should also support "sets" (collections in OAI terms. See Sets) and Selective Harvesting. These should map to collections, which Discovery calls "editions"). OAI interface MUST be tested against OAI repository explorer. #1155 #1156
• Simile Runway view of arbitrary sets of sources.
• Simile Timeline view of arbitrary sets of sources. Now part of muruca_widgets
• Sitemap and Semantic Sitemap #1140
• Simple search engine (search by metadata) along with full text search with external exist
• Linux installation detailed instructions (contact Sindre) (install instructions will work for Linux as well)

More requirements (To be included in future releases)

• Integration with Juxta
• Image annotation (Romeo, Simone, Daniel: Writes specs, make it generic, attention to philospace) #1113
• SWORD compliant submission service
• Talia stores identities for philospace. Users post their rdf notebooks on talia. (Solution: Talia and Philospace shares users identities) Admin interface to list, view, download, delete based on activescaffold.
• User profiles, bookmarks, my talia
• Simple backend
• Possibility to define required metadata fields for each source type.
• Cms integration. Done some tests with Radiant on Glassfish, latest release doesn't work but the previous one does.
• Image annotation: This is a killer feature. Needs to be implemented in IIP.
• Publication of philospace annotations (with workflow?)
• Faceted browsing (solr+ruby, solr+rdf).

SOLR would also be an interesting solution for the normale search engine. It's a stand alone search servlet, so it could nicely complement eXist (which we can keep to search in XML files).

• Graph view (see this) click on "Grafo". We should use this library!
• New IIP viewer. See Paolo's requirements at IipClientRequirements
• Produce Nines-RDF out of the box
• Tagging (limited ontology based "tagging"? E.g. geo from geonames vocab)
• Source rating
• Source plain text comments --> solved with Philospace annotations ??
• Very simple SKOS editor for creating "concept" sources, interface to view them
• Preinstalled CIDOC? Basic Subclassing? See also CidocInTalia
• Direct SPARQL interface (allow !ActiveRDF to handle SPARQL queries directly if the backend supports it)
• (Author libraries: Can we integrate Dir Van Hulle's application based on Apache Cocoon?)