How would one go about hiding restricted bitstreams in DSpace 3.1 with
XMLUI, using the Kubrick theme?
On Tue, Jun 18, 2013 at 4:10 AM, helix84 heli...@centrum.sk wrote:
Hi Jessica,
copy this mets:file template over to your theme, in order to override it:
Hi to everybody,
after reading all the messages I don't see it clear, I have a file in a
bundle that I embbed in a viewer.
I would like to check if the user has the privileges to access to the
file to include or not the viewer, I think that this is only possible
modifying some code to delete
On Thu, Feb 13, 2014 at 10:31 AM, Joan Caparrós joan.capar...@csuc.cat wrote:
Hi to everybody,
after reading all the messages I don't see it clear, I have a file in a
bundle that I embbed in a viewer.
I would like to check if the user has the privileges to access to the
file to include or not
Hi all,
is there a possibility to hide bitstreams in DSpace?
We have some bitstreams which should not be accessed by everybody.
Currently we restrict their access so that only a special group can
access them. So people who don't belong to this group can't open the
files, but they can see that
Hi Jessica,
copy this mets:file template over to your theme, in order to override it:
https://github.com/DSpace/DSpace/blob/dspace-3.1/dspace-xmlui/src/main/webapp/themes/Mirage/lib/xsl/aspect/artifactbrowser/item-view.xsl#L388
Them make the following modifications to the XSL file that contains
On Tue, Jun 18, 2013 at 11:13 AM, M. Àngels Pulido
m.angels.pul...@uvic.cat wrote:
If you select Metadata files, when you Upload a new bitstream, this
bitstream is not visible.
That's right, files in other bundles than ORIGINAL or CONTENT will be
hidden by default. The problems with this
Yes
Helix, to us this approach
works because we want to hide the bitstream
that is a
.pdf where the user put the
permission to publish their work: article, book, etc. in our repository and therefore, this document contains
On Tue, Jun 18, 2013 at 12:06 PM, M. Àngels Pulido
m.angels.pul...@uvic.cat wrote:
Yes Helix, to us this approach works because we want to hide the bitstream
that is a .pdf where the user put the permission to publish their work:
article, book, etc. in our repository and therefore, this
8 matches
Mail list logo
