Robert Tansley ha scritto:
On 01/09/07, Mark Diggory [EMAIL PROTECTED] wrote:
Restricting access to Communites, Collection or Items directly is
certainly not what DSpace was designed to do.
The real issue is more that the DSpace authz model has no notion of
'know of an object's
Hi Mark et all,
Restricting access to Communites, Collection or Items directly is
certainly not what DSpace was designed to do.
you are right, but the question now is should DSpace support this type
of needs? well, I (and you seeing last line of your response) think that
it should.
This is
mmm... I'm really wrong
I'm sorry but I should read more closely your wiki page ;-)
You have modified some part of retrieval API so your patch is not only
for JSPUI, as you have noted it doesn't works on oai-pmh because there
are others methods (as findAll() used by oai-pmh) for retrieval
Hi Lucas,
thanks for you clear wiki page, it should be useful for someone others.
Please note that your patch is *only* on user interface (JSPUI) so the
communities and the collections that you hide are visible on oai-phm
response (if you think you can add this info in Things to do).
A more
Restricting access to Communites, Collection or Items directly is
certainly not what DSpace was designed to do.
This is really one of the real pain points of DSpace IMO. There are
just so many places where the assumption that a container (Community/
Collection/Item) will be unrestricted. To
5 matches
Mail list logo
