need info on search and content definition

[strinchero]

Hi all,
i'm evaluating alfresco to replace an existing dms, and i need some clarification,:

Search: is it possible to have a non-autenticated user find all the published document (of some type for example), but to be forced to log in to see the actual document ?
In other words, the guest user may serch item (and see only some info, like title, date ecc) and see if there some interesting (to him) docs. But for accessing the whole content, he must be logged in (non-guest, of course).

Content type: i need to have a doc that has it's property readeble, but the content itself may not be readable. As an example, i may have an article, whos short descriptio, abstract and all the info on it are readeble by all, but the pdf of the article need a specific permission to be read (downloaded).

Then, i need to have a document with attachment (an article with 2 images, as an example). Is that doable on a single document, or i'have to define a folder-type (the article) who contains both images ? In that situation, is hard to write the interface to manipulate folder and contents (so a user only see an 'article' and the implementation details remains hidden) or it's not much different ?

tnks in advance,
Silvano

[strinchero]

I have asked stupid questions ?

[andy]

Hi

Search is restricted to what you have permission to read at the API layer.
You can code to do what you want but bit is not exposed in the public API.
There is no way of asking for authentication depending on what you try and view.



The lower level permissions are available to do what you want (read properties, read children and read content). Again, they are not exposed with the current API. They are grouped together as Read and exposed as Consumer at the moment.




You can link things as parent-child relationships or via associations.

There are several ways:

1) Create the images as non folder/content types (then they should not be shown)

2) Add your own aspect defining your own parent-child relationship  that differs from the one defined in file/folder. These should not be shown.

3) Manage the images via non child associations.

Regards

Andy