[Dspace-tech] Restricting Bitstream Access Based on IP-Range
I can't find anything on this in the DSpace site or wiki, and I think this may not be possible, but is anyone aware of a way, without using a proxy server, to block access to the bitstream of an object based on an IP range, rather than group membership? We have some objects that we want to make accessible to anyone on-campus, using our campus IP scheme, but not off-campus. I'm aware that this is not an air-tight way of preventing the public from accessing the bitstream, and we're OK with that. It is fine with us if the object's metadata is available from any IP address; the only thing we would like to prevent is off-campus access to the bitstream. Thanks in advance for any help on this one... -- Stacy Pennington Rhodes College penning...@rhodes.edu (901) 843-3968 -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] options about postgresql.
Hi there, I'm trying to install dspace 1.6.0-rc1. In the dspace-manual.pdf provided, the chapter 3 about install said that postgresql 8.x have to be compiled with options --enable-multibyte, --enable-unicode and --with-java. But with sources of postgresql 8.3 the command ./configure --help does not provide the options asked by dspace manual. How to compile options that does not exist ? Am i with wrong version of postgresql (provided by Debian Lenny) ? Regards, -- *Fabien COMBERNOUS* /unix system engineer/ www.kezia.com http://www.kezia.com/ *Tel: +33 (0) 467 992 986* Kezia Group -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] dc.identifier.uri dcterms.uri
Hi, I'm having an issue with mapping dc.identifier.uri to dcterms.uri despite it being mapped in DCC Crosswalk. I have created a custom dcterms input form but I'm unable to pick it when I create a field or value-pair. I wish dcterms.uri to overide dc.identifier.uri in the Item Record and appear in the generated xml Am I missing something? Cheers Kevin Kevin Evans MA Web Services Developer, Integration and Webservices, Room 901, 9th Floor, Laver Building University of Exeter, Exeter, Devon, EX4 4QE 01392 725573 +447775027574 http://my.exeter.ac.uk http://my.exeter.ac.uk/ This email and any attachment may contain information that is confidential, privileged, or subject to copyright, and which may be exempt from disclosure under applicable legislation. It is intended for the addressee only. If you received this message in error, please let me know and delete the email and any attachments immediately. The University will not accept responsibility for the accuracy/completeness of this e-mail and its attachments. The University cannot guarantee that this message and any attachments are virus free. Any views or opinions expressed in this message are my own and do not necessarily represent those of the University. attachment: Kevin Evans (kevin.evans@exeter.ac.uk).vcf smime.p7s Description: S/MIME cryptographic signature -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] Help with non-running DSpace scripts
Dear colleagues, We hope someone on this list can help us understand why some scripts in the DSpace/bin directory on Windows run while some others don't. We've installed the handle server and edited the config files. We run DSpace 1.5.1 on Win 2003 server. However, when we try to run any handle server related scripts from DSpace\bin, we have the following messages: C:\DSpace\binupdate-handle-prefix 123456789 10587 'update-handle-prefix' is not recognized as an internal or external command, operable program or batch file. C:\DSpace\binstart-handle-server 'start-handle-server' is not recognized as an internal or external command, operable program or batch file. At the same time, dsrun in the same bin directory runs just fine. What should we do to make handle scripts work? Your help is really appreciated! Cheers, Stan Orlov -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Help with non-running DSpace scripts
Stan, The reason for the problems that you see are that most scripts (all those without file extensions) in that [dspace]/bin directory are actually Linux Bourne Shell scripts. In DSpace 1.5.x only the 'dsrun.bat' script works on Windows (it's a Windows/MS-DOS batch file). In DSpace 1.5.x, if you want to run one of the other scripts on Windows, you'd need to open up the script file (e.g. update-handle-prefix) and type in the class name which appears after the $BINDIR/dsrun. So, as an example, instead of running update-handle-prefix on Windows, you'd run: dsrun org.dspace.handle.UpdateHandlePrefix As another example, instead of running start-handle-server on Windows, you'd run: dsrun -Ddspace.log.init.disable=true -Dlog4j.configuration=log4j-handle-plugin.properties net.handle.server.Main [handle-dir] [path to handle server log file] Obviously, this is not ideal, and makes it difficult to run commands on Windows. So, in DSpace 1.6.0 (to be released in Feb), we've reworked this, so that all commands (on Linux or Windows) can be run from a common dspace script. So, in DSpace 1.6.0, you'd just run '[dspace]/bin/dspace update-handle-prefix' on either Linux, Mac or Windows. - Tim On 1/25/2010 11:39 AM, Stan Orlov wrote: Dear colleagues, We hope someone on this list can help us understand why some scripts in the DSpace/bin directory on Windows run while some others don't. We've installed the handle server and edited the config files. We run DSpace 1.5.1 on Win 2003 server. However, when we try to run any handle server related scripts from DSpace\bin, we have the following messages: C:\DSpace\binupdate-handle-prefix 123456789 10587 'update-handle-prefix' is not recognized as an internal or external command, operable program or batch file. C:\DSpace\binstart-handle-server 'start-handle-server' is not recognized as an internal or external command, operable program or batch file. At the same time, dsrun in the same bin directory runs just fine. What should we do to make handle scripts work? Your help is really appreciated! Cheers, Stan Orlov -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Restricting Bitstream Access Based on IP-Range
Hello Stacy, this is not directly configurable, but you can achieve it by a combination of IP-based authentication and the standard DSpace resource policies. Create an IP based group for the members of your university and a resource policy that restricts the bitstream access to members of that group. During ingest the item and its bitstream(s) derive their resource policies from the DEFAULT_ITEM_READ and DEFAULT_BITSTREAM_READ. So setting DEFAULT_BITSTREAM_READ to the group which includes your university members will restrict the access of the newly ingested bitstreams to this group. For bitstreams in already ingested items you got to use the advanced policy tool to change the resource policies. Hope that helps Claudia Jürgen I can't find anything on this in the DSpace site or wiki, and I think this may not be possible, but is anyone aware of a way, without using a proxy server, to block access to the bitstream of an object based on an IP range, rather than group membership? We have some objects that we want to make accessible to anyone on-campus, using our campus IP scheme, but not off-campus. I'm aware that this is not an air-tight way of preventing the public from accessing the bitstream, and we're OK with that. It is fine with us if the object's metadata is available from any IP address; the only thing we would like to prevent is off-campus access to the bitstream. Thanks in advance for any help on this one... -- Stacy Pennington Rhodes College penning...@rhodes.edu (901) 843-3968 -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech -- Claudia Jürgen Eldorado - Repositorium der TU Dortmund Universitätsbibliothek Dortmund Vogeplothsweg 76 D-44227 Dortmund Tel.: 0049-231-755-4043 -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Help with non-running DSpace scripts
Thank you, Tim! Worked like a charm! Looking forward to 1.6.0 now :) Cheers, Stan On Mon, Jan 25, 2010 at 2:18 PM, Tim Donohue tdono...@duraspace.org wrote: Stan, The reason for the problems that you see are that most scripts (all those without file extensions) in that [dspace]/bin directory are actually Linux Bourne Shell scripts. In DSpace 1.5.x only the 'dsrun.bat' script works on Windows (it's a Windows/MS-DOS batch file). In DSpace 1.5.x, if you want to run one of the other scripts on Windows, you'd need to open up the script file (e.g. update-handle-prefix) and type in the class name which appears after the $BINDIR/dsrun. So, as an example, instead of running update-handle-prefix on Windows, you'd run: dsrun org.dspace.handle.UpdateHandlePrefix As another example, instead of running start-handle-server on Windows, you'd run: dsrun -Ddspace.log.init.disable=true -Dlog4j.configuration=log4j-handle-plugin.properties net.handle.server.Main [handle-dir] [path to handle server log file] Obviously, this is not ideal, and makes it difficult to run commands on Windows. So, in DSpace 1.6.0 (to be released in Feb), we've reworked this, so that all commands (on Linux or Windows) can be run from a common dspace script. So, in DSpace 1.6.0, you'd just run '[dspace]/bin/dspace update-handle-prefix' on either Linux, Mac or Windows. - Tim On 1/25/2010 11:39 AM, Stan Orlov wrote: Dear colleagues, We hope someone on this list can help us understand why some scripts in the DSpace/bin directory on Windows run while some others don't. We've installed the handle server and edited the config files. We run DSpace 1.5.1 on Win 2003 server. However, when we try to run any handle server related scripts from DSpace\bin, we have the following messages: C:\DSpace\binupdate-handle-prefix 123456789 10587 'update-handle-prefix' is not recognized as an internal or external command, operable program or batch file. C:\DSpace\binstart-handle-server 'start-handle-server' is not recognized as an internal or external command, operable program or batch file. At the same time, dsrun in the same bin directory runs just fine. What should we do to make handle scripts work? Your help is really appreciated! Cheers, Stan Orlov -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Restricting Bitstream Access Based on IP-Range
Thanks! That is exactly what I needed to know. I had never noticed the IP authentication options before in the dspace.cfg or admin guide. So, I'm assuming that, if I have a DSpace group in my repository called RHODES and I wanted to assign any 10.x.x.x IP addresses to that group, I would enable IP auth in the stackable authentication and then use this line in dspace.cfg to let DSpace know to put anyone from the 10.x.x.x range into that group, unless they otherwise authenticate as a LDAP user (LDAP comes first in our stackable auth list): authentication.ip.RHODES = 10 Correct? -- Stacy Pennington Rhodes College penning...@rhodes.edu (901) 843-3968 -Original Message- From: Claudia Juergen [mailto:claudia.juer...@ub.tu-dortmund.de] Sent: Monday, January 25, 2010 1:08 PM To: Pennington_Stacy Cc: dspace-tech@lists.sourceforge.net Subject: Re: [Dspace-tech] Restricting Bitstream Access Based on IP-Range Hello Stacy, this is not directly configurable, but you can achieve it by a combination of IP-based authentication and the standard DSpace resource policies. Create an IP based group for the members of your university and a resource policy that restricts the bitstream access to members of that group. During ingest the item and its bitstream(s) derive their resource policies from the DEFAULT_ITEM_READ and DEFAULT_BITSTREAM_READ. So setting DEFAULT_BITSTREAM_READ to the group which includes your university members will restrict the access of the newly ingested bitstreams to this group. For bitstreams in already ingested items you got to use the advanced policy tool to change the resource policies. Hope that helps Claudia Jürgen I can't find anything on this in the DSpace site or wiki, and I think this may not be possible, but is anyone aware of a way, without using a proxy server, to block access to the bitstream of an object based on an IP range, rather than group membership? We have some objects that we want to make accessible to anyone on-campus, using our campus IP scheme, but not off-campus. I'm aware that this is not an air-tight way of preventing the public from accessing the bitstream, and we're OK with that. It is fine with us if the object's metadata is available from any IP address; the only thing we would like to prevent is off-campus access to the bitstream. Thanks in advance for any help on this one... -- Stacy Pennington Rhodes College penning...@rhodes.edu (901) 843-3968 -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech -- Claudia Jürgen Eldorado - Repositorium der TU Dortmund Universitätsbibliothek Dortmund Vogeplothsweg 76 D-44227 Dortmund Tel.: 0049-231-755-4043 -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
