Project Priorities
Prioritized list of remaining subprojects based on input from various group discussions.
- continue to upgrade and tweak the SKEN version of Epoz (let's call it EpozSK for now).
- handle special characters (especially important for Hawaiian species and "Other Names").
- integrate with bibliography tools for linking to references.
- integrate with Exhibits tools for images, tables, etc.
- bibliography - select/create a bibiliography tool.
- bibliography folder object or some other container.
- bibref objects and data entry/edit template
- even if we select an existing product, we will probably need to do some work on the format of individual entries.
- add "generic" biliography entry to handle existing documents where biliographic references are not proken down into individual fields
- add DOI field to all entry formats.
- add code to SkenArticle to popup bibliography references when clicked.
- code to translate BNA references into whatever format is selected.
- create an Exhibits content model to hold images, audio, video, tables, etc.
- exhibits folder object or some other container.
- exhibit objects and data entry/edit templates for each
- all entries want sequence, caption, artist and rights fields (anyothers ?)
- images want "class" field (type=photo, figure, map, etc.)
- images need option to have thumbnail verison of image
- audio and video want image plus audio/video stream
- table input/edit - separation of data from display
- matrix or grid data object
- table display obejct
- Bulk BNA content load utilities
- bulk download from Fatwire with ALL data.
- what about images ?
- how to handle audio/video galleries ?
- refactor prototype conversion tools to handle all Fatwire data.
- load directly to SkenArticle and associated content types.
- formalize the Sken document content models into Plone Products.
- develop new SkenArticle content type based on PloneArticle.
- update Article with the customized templates built for demo case.
- make Article aware of extra metadata such as Author, Taxonomy, etc.
- add plain document model (similar to ordinary Plone Document but aware of PloneArticle extras such as Galleries and navigation
- add single embedded picture model
- Gallery object for images and streaming media.
- image content model that deals with enhanced image content type from Exhibits - thumbnail, class, sequence, alt, rights, artist
- handle streaming media content type
- Scholarly Journal document type
Archetypes object that knows how to build a content hierarchy for a Scholarly Journal. - Journal as a folderish object that knows about Volumes.
- Volume as a folderish object that knows about Issues.
- Issue as a folderish object that knows about Articles.
- portal for "within Issue" navigation
- metadata "inheritance" from parent object in hierarchy.
- taxonomy "awareness" among objects
- tool to create default Article templates.
- High-priority search engine enhancements.
- improve search results display - include Issue in results
- search by species (from home page) - BNA specific item
- Integrate workflow management tools
- staging - copy of content for formal edit, review, update cycle.
- workflow for creating Article in Scholarly Journal
- workflow for editing Article in Scholarly Journal
- mechanism for inserting reviewer comments in Articles
- roles and permissions for each step in workflow.
- Upgrades to SkenArticle content type
- native XML content model and appropriate content objects
- finalize XML Schemas
- granularity of access to content
- Advanced search engine enhancements
- Author/revisor search
- citation/reference search
- advanced keyword search
- find keyword(s) within Article
- find keyword(s) within Issue (equivalent to species in BNA)
- find keyword(s) within taxonomic Family (BNA specific) - this requires Journal/Issue/Article to be "taxonomy aware" (see Scholarly Journal document type in number 5 above.
- Mechanism for repurposing content
- Combine sections/topics into new articles
- Use sections/topics in educational materials
- Mechanism for adding footnotes to content and referencing them.
- Mechanism for annotating content
- Article based discussion forums
- Repository enhancements and alternatives
- enhanced version control
- Adaptable Persistence Engine (APE) - ability to store data outside ZODB.
- file system based - useful for many types of exhibits, essential for streamed data types
- FEDORA ?