- From: Ed Summers <ehs@pobox.com>
- Date: Fri, 5 Feb 2010 06:43:41 -0500
- To: W3C e-Gov IG <public-egov-ig@w3.org>
On Thu, Feb 4, 2010 at 7:56 AM, Chris Beer <chris-beer@grapevine.net.au> wrote: > The architecture for the repository will be a customised Sharepoint document > library (SQL backend) with added fields etc for RDA and DC based metadata > (AGLS for those who know about it). A "Cool URI" system will be used. Cover > sheets and versioning will be used. A Persistant URL resolver service > (Handle) will be used, either in-house or via a third party, also in the gov > domain - this will assist in archival management and citation. Web crawling > will be the primary third party method of indexing our content, but we will > also be supporting RSS feeds (looking into Atom atm as well) and Web > Services. Public interface will be a search form which searches on the > metadata fields, not the Sharepoint fields. > > Thoughts? Sounds like a fun project Chris. I wonder have you all thought at all about how content gets into the repository? I guess one use case I would be interested in exploring would be an mechanism that allowed trusted partners to push content to the repository. This would allow your service to become part of a publishing workflow that wouldn't require people to upload documents manually. If you do have to provide some functionality in this area you might want to look at AtomPub (RFC 5023) [1]. It's basically a RESTful, webarch friendly way of pushing content using HTTP. As a point of reference the digital library / repository community has seen some uptake/experimentation in the Fedora, DSpace and Eprints worlds via the Simple WebService Offering Repository Deposit project [2]. //Ed [1] http://bitworking.org/projects/atom/rfc5023.html [2] http://swordapp.org/
Received on Friday, 5 February 2010 11:44:14 UTC