Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-slide Wiki" for change notification.
The following page has been changed by DarrenHartford: http://wiki.apache.org/jakarta-slide/Slide%2eSDA ------------------------------------------------------------------------------ * File-based XML for metadata repository, use Lucence to speed up searching. * Allow for a 'FAX' Namespace to hold that related data as well as the default 'DAV' for the DASL searching. * File-based object storage for the files. - * Archive a 'store' by Month/Year based on receivedate (JAN04, FEB04, etc) to CD. Maybe sub-CD's for each department if they need their own. + * Archive a 'store' by Month/Year based on receivedate (JAN04, FEB04, etc) to CD. Maybe sub-CD's for each department if they need their own. 'archive store' = readonly. * Allow for searching across multiple stores that are mounted in Slide as a single group (all faxes) or by department (Accounting faxes). * Optional: versioning (not useful in this usecase, but would be for others). - User requirements - this is where it really matters. Allow the user to utilize Jakarta Slide in a way that makes sense. + User requirements for SDA - this is where it really matters. Allow the user to utilize Jakarta Slide in a way that makes sense. * For new Namespaces like 'FAX', require a DTD or Schema if want to restrict/enforce attributes/propertys. * Export based on range of data to another store (for archive?). + * SDA default setup has good default roles, such as 'searcher', 'writer', 'admin' that can be mapped to Realm-based security. + * Default UI for a 'searcher' user via web that is useful and adaptive to namespaces (allows to search in 'FAX' namespace based on 'receivedate' attribute defined by DTD/Schema). Also allow user to quickly identify search range, whether single store or a defined group. + * Allow for easy addition of existing archived stores (i.e. on CD/DVD, or on remote or local file systems). + * Allow for easy grouping of stores for cross-search context. + User Responibilities: + * User is responsible for 'injecting' the binary file and related data into SDA. SDA simply allows them to do so and handles storing and searching for documents. Recommend WebDAV protocol, WCK for Java, sample in .NET, etc. + * User is responsible for backup/restore of the filesystem where SDA archives data. + * User is responsible for setting up Realm security (tomcat/jboss), map to roles. However, SDA should have some examples for common use-cases (ActiveDirectory, Tomcat configured users, etc.). + --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
