I am unsure what this point means. As far as I know, campsite has
organisation of the content derived from paper newspaper:
It devides each publication to sections.
This way, you can sell your publication as the whole thing, or allow
limited subscription to sections defining for each subscriber, what kind
of content hehas subscribed.
After you go through this, you can create first issue and release first
issue of your publication.
There is not subscription for issue in meaning "you can buy only number
3,4,6 and 7) as far as I know, because the subscription is time based.
Next think you should know about subscription is its connection to
template language. You can undestand the subscription in a way of flag,
which means, that the template designer can decide, what content is
limited to subscribers and which not.
For example he can decide, that any content from the homepage is free,
but once the article is off homepage, it is accessible to subscribers
only.
Or you can define topic "public" and all content having this topic is
displayed to readers without need of subscription.
So as you can see from examples, thanks to the subscription model
Campsite use, you can design almost any access model you need and the
only limitation is, it should count with time, not with issues.
And only a short line about individual and group subscriptions.
I usually explain this to marketing people in following way:
The subscriber is either individual, or organization.
In case of individual, it is usefull for him to use username/password
based authentification, because he can access the content from anywhere.
In case of organization, it depends.
Sometimes there is only several people in big organization interested in
your content. So you choose several username/password accesses and
system handle them as individuals.
Or organization is a library, that want the content for any amount of
visitors, but the limitation is they should use only PCs inside library.
In that case I recommend IP based authentification.
I hope this explains at least something to you.
Ondra
On Mon, 2005-10-03 at 19:54 +0200, phorum@code.campware.org wrote:
> 6. Be able to include different versions of the material in a subscription (to cater for those migrating from one version of the software to another).
The ip based authentication sounds like just what I need for "group" subscriptions.
Time based subscriptions are what I need.
Formatting: the examples given are basically what I need - I will have to look at how to handle headings present in the "master" version.
Payment/Subscription integration: Yes, I'm coming around to the view that there will need to be a human bridge between the two - especially with an OS solution.
The shared server issue is a show stopper for now - when is it likely that installation on a shared server will be possible (without the access outlined in the reply to my earlier post)?
I've looked at the Cream manual - no mention of it not being possible to install this on a shared server with typical access privileges. Would this be possible?