Index: openacs-4/packages/download/www/doc/requirements.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/download/www/doc/requirements.html,v diff -u -r1.1 -r1.2 --- openacs-4/packages/download/www/doc/requirements.html 20 Apr 2001 20:51:10 -0000 1.1 +++ openacs-4/packages/download/www/doc/requirements.html 23 Feb 2002 05:15:35 -0000 1.2 @@ -7,14 +7,14 @@
ACS 4.x has a file storage module, so an obvious question is: +
OpenACS 4.x has a file storage module, so an obvious question is: "Why do we need a seperate download module?" The download module is targeted at a different usage pattern and interface. The intent of the download module is to provide an online repository @@ -33,7 +33,7 @@
There are thousands of independent developers all over the world - writing their own ACS packages. Without a canonical distribution + writing their own OpenACS packages. Without a canonical distribution point finding the packages you need becomes a formidable task, forcing developers to duplicating each others efforts. The download module allows us to setup a package repository service @@ -45,7 +45,7 @@
- The ACS download package provides an application for managing file + The OpenACS download package provides an application for managing file distribution.
@@ -74,9 +74,9 @@ Joe Contributer (currently working for Joe.com) writes a piece of software used to do knowledge management (KM) for the ACS. He packages his code using the APM. Joe - feels that others could gain from using his knew package so he uploads - it the the ArsDigita Package Repository. Since it is in APM format in + href=/doc/packages>APM. Joe + feels that others could gain from using his new package so he uploads + it to the OpenACS Package Repository. Since it is in APM format, in one step a package, version, vendor, owner and description data are all uploaded (extracted from the .info file). @@ -86,7 +86,7 @@ to not allow users to download versions pending approval. That forces her to download Joe's package from the admin pages and install it. She notices that it isn't malicious in any way and doesn't harm her - ACS installation so she approves it to go live on her package + OpenACS installation so she approves it to go live on her package repository. Joe is informed via email that his package was approved (because Jane set this configuration parameter). @@ -96,15 +96,15 @@ a package repository and finds Joe's KM package. He notices that many other users have downloaded the package and have made comments praising the package as well as Joe.com. Since Ben is a - follower by heart he decides to download the package as well and + follower by heart, he decides to download the package as well and install it on his system. (Ben's crafty friend Alyssa later informs Ben that he could have just had the APM install directly from the repository url).Benny Beancounter loves to learn about who's downloading files from - his site and what reasons they give for downloads. On a frequent basis + his site and what reasons they give for downloads. On a frequent basis, Benny visits the download packages admin pages and views a report of how many downloads occured for each file. He then drills down on a particular file and views a list of the users who downloaded the file @@ -114,7 +114,8 @@
10.0 Versioned File Storage
- ACS Download must provide versioned file storage. + OpenACS Download must provide versioned file storage.
20.0 User Tracking
- ACS Download must store information about which users have downloaded which files (including versions). + OpenACS Download must store information about which users have downloaded which files (including versions).
20.0 Package Based Meta Information
- ACS Download must be able to store arbitrary meta information on a per package basis. + OpenACS Download must be able to store arbitrary meta information on a per package basis. i.e. All files provided by this instance of the package require the fields x, y and z.
@@ -316,6 +317,13 @@