[Dspace-tech] DSpace Request Copy Add-on
Dear Team, I would like to run DSpace Request Copy Add-on module on DSpace 3.2 version, I have read on DSpace Request Copy Add-on online page(https://wiki.duraspace.org/display/DSPACE/RequestCopy) that the module is currently running on the following dspace versions : dspace 1.6.2, 1.7.2 & 1.8.2 If there is anyone on who has configured the module to run on dspace 3.2 or dspace 4.2 please share with me possible steps. Regards, Lewatle This communication is intended for the addressee only. It is confidential. If you have received this communication in error, please notify us immediately and destroy the original message. You may not copy or disseminate this communication without the permission of the University. Only authorised signatories are competent to enter into agreements on behalf of the University and recipients are thus advised that the content of this message may not be legally binding on the University and may contain the personal views and opinions of the author, which are not necessarily the views and opinions of The University of the Witwatersrand, Johannesburg. All agreements between the University and outsiders are subject to South African Law unless the University agrees in writing to the contrary. -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] [Dspace-general] Regarding Ranking of Repositories
Dear German, Thanks for your support. I understand this can be difficult to implement or that needs time to develop. No problem for applying the proposals later or not applying at all. Best regards, Germán Biozzoli escribió: > I think that > > >> * Rule #7 (IRs that use more than 3 different numeric (or useless) codes >> in their URLs will be excluded.). It is unclear how they would determine >> this, and what the effect may be on DSpace sites worldwide. Again, >> looking at the common DSpace URL paths above, if a file had a "numeric" >> name, it may be excluded as DSpace URLs already include 2-3 numeric >> codes by default ([prefix],[id], and [sequence] are all numeric). > > I have a personal example. 20 years ago my email admin decided my > email account should be 'dctfa11', abusing from your notation > ([prefix],[id], and [sequence]). After several years it was possible > to change to 'isidro.aguillo'. > > I going to use the URL of my papers to cite them, to marketing them, > to copy in my CV, . Please, help me translating /56/89/567894 into > aguillo2014b > > --- > has no posible conceptual discussion: > > http://www.w3.org/2013/dwbp/wiki/URI_Design_and_Management_for_Persistence > > And of course, correct URIs have effects over SEO, that is an inherent > responsability to IRs platforms. As a DSpace implementor I understand that > it could have no inmediate solution, but to me it's undoubted the correct > requirement for future DSpace versions. > > Regards > German > > > > 2014-09-03 19:53 GMT-03:00 Isidro F. Aguillo : > >> Dear Tim, >> >> Tim Donohue escribió: >> >> > Hello Isidro, >> > >> > DuraSpace (the stewarding organization behind DSpace and Fedora >> > repository software) was planning to send you a compiled list of the >> > concerns with your proposal. As you can tell from the previous email >> > thread, many of the users of DSpace have similar concerns. Rather than >> > bombard you with all of them individually (which you could see from >> > browsing the thread), we hoped to draft up a response summarizing the >> > concerns of the DSpace community. >> >> Thanks a lot. That is far beyond my better expectations. >> >> >> > Below you'll find an initial draft of the summarized concerns. The rule >> > numbering below is based on the numbering at: >> > http://repositories.webometrics.info/en/node/26 >> > >> > --- Concerns with the Proposal from Ranking Web of Repositories >> > >> > * Rule #2 (IRs that don't use the institutional domain will be excluded) >> > would cause the exclusion of some IRs which are hosted by DSpace service >> > providers. As an example, some DSpaceDirect.org users have URLs >> > https://[something].dspacedirect.org which would cause their exclusion >> > as it is a non-institutional domain. Many other DSpace hosting providers >> > have similar non-institutional domain URLs by default. >> >> >> Major issue. Repository is not another bibliographic database, it is >> the archive of the academic output of the institution. And as such it >> should be iron brand. >> >> If .. the institution is very small or in a country with limited >> resources the hosting option is perfectly valid and we will do an >> exception. But in these cases, Is not a redirection possible? >> >> If .. the problem is related to governance we should not reward the >> institution bad practice. >> >> >> > * Rule #4 (Repositories using ports other than 80 or 8080) would wrongly >> > exclude all DSpace sites which use HTTPS (port 443). Many institutions >> > choose to run DSpace via HTTPS instead of HTTP. >> >> No problem adding a few more ports to the short list >> >> >> > * Rule #5 (IRs that use the name of the software in the hostname would >> > be excluded) may also affect IRs which are hosted by service providers >> > (like DSpaceDirect). Again, some DSpaceDirect customers have URLs which >> > use *.dspacedirect.org (includes "dspace"). This rule would also exclude >> > MIT's IR which is the original "DSpace" (and has used the same URL for >> > the last 10+ years): http://dspace.mit.edu/ >> >> This is easy. Imagine that the people at MIT decide next week they >> prefer eprints or other new software. A repository is a repository, >> why not a final one like?: >> >> repository.mit.edu >> >> On the other side, I wrote all my papers using MS Word and never cited >> that fact in any of them, less of all in the authorship >> >> >> >> > * Rule #6 (IRs that use more than 4 directory levels for the URL address >> > of the full texts will be excluded.) may accidentally exclude a large >> > number of DSpace sites. The common download URLs for full text in DSpace >> > are both are at least 4 directory levels deep: >> > >> > - XMLUI: [dspace-url]/bitstream/handle/[prefix]/[id]/[filename] >> > - JSPUI: [dspace-url]/bitstream/[prefix]/[id]/[sequence]/[filename] >> > >> > NOTE: "prefix" and "id" are parts of an Item's Handle >> > (http://hdl.handle.net/), which is the persisten
Re: [Dspace-tech] [Dspace-general] Regarding Ranking of Repositories
Dear colleaugue, User is user, not any casual reader. A non-casual reader of an academic paper is usually another scientist (a Higgs boson text is not for everybody), and any professional (including junior ones like PhD students) scientist is or is going to be an author. Best regards, sharad escribió: > Hi, > > Most of us will do agree with the fact that authors themselves (or > funder of research/repository) are not the sole end users of a > repository. In contrary major end users are non-authors or people who > have not contributed to a repository and are just the users of the > repository. > > If what ever changes that are proposed are for the better user > experience of end-user, let us not assume that the end users are only > authors. > > Best Regards, > Sharad > > > On Thu, Sep 4, 2014 at 2:55 AM, Anton Angelo wrote: >> Hi Isidro, >> >> As a librarian/technologist managing a institutional repository I have to >> disagree with you on the definition of our end users. There are two ways >> to look at this, and neither end up with the authors as end users. >> >> An idealistic approach would see the final readers of the items as the end >> users. They are the ones, defined by various OA declarations, the ones for >> whom we are doing this. >> >> A pragmatic approach would say the funders of the research are the end >> users, as they are demanding the output of their funding to be made OA. >> >> The latter group are the ones your service is most useful for, in >> determining the performance of their outputs - the more visible, the better >> vehicle for publication. >> >> I am beginning to think that rankings are not a very useful manner in which >> to compare IRs, but a list of platform agnostic best practice standards >> (like the orange book for security, back in the day) is the way forward. >> Though I have extensively used the service in my research on IR >> effectiveness, that was mostly because the repository I manage has a high >> ranking, and it was useful to promote it internally. This kind of behaviour >> usually ends up in 'gaming', and is counterproductive - exactly what OA is >> trying to get away from (h-index, impact factor, etc). >> >> IRs are really about getting the right output to the right person - even one >> download can be a total success. I think in the future altmetric tools are >> probably going to be more use than a ranking service, as useful as it has >> been in the past - provided they report on the work in OA being done in the >> global south. >> >> aa >> >> >> >> >> >> >> On 4 September 2014 09:12, Isidro F. Aguillo >> wrote: >>> >>> Dear Stuart, >>> >>> I do not know if you understand the ultimate purpose of Open access >>> initiatives in general and the institutional repositories in >>> particular. But I think you are mising the central point that the >>> end-users should guide the design of the repository according to their >>> real needs. >>> >>> Well, in OA the end users are the authors of the papers, their >>> institutions that fund the research and host the papers and the >>> librarians who manage the repository. In this scenario the software >>> developers task is to fulfill in the most professional way the needs >>> of the authors. >>> >>> Regarding authors needs, the W3C organization and its 'cool' proposals >>> is arbitrary basically because they do not know how scholarly >>> communication works, and the aims and methods of OA. They are not >>> stakeholders for us. >>> >>> In any case, I will prefer and thank from you comments on the specific >>> proposals and not a general, ambigous and unsupported global criticism. >>> >>> Best regards, >>> >>> >>> Stuart Yeates escribió: >>> >>> > I'm not sure that knee-jerk reaction to an arbitrary list of bad >>> > practice is a good place to start and seems like a really bad driver >>> > for software development. >>> > >>> > Maybe we should be talking to our fellow implementers and building >>> > on the work of http://www.w3.org/Provider/Style/URI.html, >>> > http://www.w3.org/TR/cooluris/, >>> > http://www.openarchives.org/OAI/openarchivesprotocol.html, etc. to >>> > build a compilation of _best_ practice. >>> > >>> > Cheers >>> > stuart >>> > >>> > -Original Message- >>> > From: Tim Donohue [mailto:tdono...@duraspace.org] >>> > Sent: Wednesday, 3 September 2014 8:49 a.m. >>> > To: Isidro F. Aguillo; dspace-tech@lists.sourceforge.net >>> > Cc: Jonathan Markow; dspace-gene...@lists.sourceforge.net >>> > Subject: Re: [Dspace-general] [Dspace-tech] Regarding Ranking of >>> > Repositories >>> > >>> > Hello Isidro, >>> > >>> > DuraSpace (the stewarding organization behind DSpace and Fedora >>> > repository software) was planning to send you a compiled list of the >>> > concerns with your proposal. As you can tell from the previous email >>> > thread, many of the users of DSpace have similar concerns. Rather >>> > than bombard you with all of them individually (which you could see >>> > from browsing t
Re: [Dspace-tech] [Dspace-general] Regarding Ranking of Repositories
I think that > * Rule #7 (IRs that use more than 3 different numeric (or useless) codes > in their URLs will be excluded.). It is unclear how they would determine > this, and what the effect may be on DSpace sites worldwide. Again, > looking at the common DSpace URL paths above, if a file had a "numeric" > name, it may be excluded as DSpace URLs already include 2-3 numeric > codes by default ([prefix],[id], and [sequence] are all numeric). I have a personal example. 20 years ago my email admin decided my email account should be 'dctfa11', abusing from your notation ([prefix],[id], and [sequence]). After several years it was possible to change to 'isidro.aguillo'. I going to use the URL of my papers to cite them, to marketing them, to copy in my CV, . Please, help me translating /56/89/567894 into aguillo2014b --- has no posible conceptual discussion: http://www.w3.org/2013/dwbp/wiki/URI_Design_and_Management_for_Persistence And of course, correct URIs have effects over SEO, that is an inherent responsability to IRs platforms. As a DSpace implementor I understand that it could have no inmediate solution, but to me it's undoubted the correct requirement for future DSpace versions. Regards German 2014-09-03 19:53 GMT-03:00 Isidro F. Aguillo : > Dear Tim, > > Tim Donohue escribió: > > > Hello Isidro, > > > > DuraSpace (the stewarding organization behind DSpace and Fedora > > repository software) was planning to send you a compiled list of the > > concerns with your proposal. As you can tell from the previous email > > thread, many of the users of DSpace have similar concerns. Rather than > > bombard you with all of them individually (which you could see from > > browsing the thread), we hoped to draft up a response summarizing the > > concerns of the DSpace community. > > Thanks a lot. That is far beyond my better expectations. > > > > Below you'll find an initial draft of the summarized concerns. The rule > > numbering below is based on the numbering at: > > http://repositories.webometrics.info/en/node/26 > > > > --- Concerns with the Proposal from Ranking Web of Repositories > > > > * Rule #2 (IRs that don't use the institutional domain will be excluded) > > would cause the exclusion of some IRs which are hosted by DSpace service > > providers. As an example, some DSpaceDirect.org users have URLs > > https://[something].dspacedirect.org which would cause their exclusion > > as it is a non-institutional domain. Many other DSpace hosting providers > > have similar non-institutional domain URLs by default. > > > Major issue. Repository is not another bibliographic database, it is > the archive of the academic output of the institution. And as such it > should be iron brand. > > If .. the institution is very small or in a country with limited > resources the hosting option is perfectly valid and we will do an > exception. But in these cases, Is not a redirection possible? > > If .. the problem is related to governance we should not reward the > institution bad practice. > > > > * Rule #4 (Repositories using ports other than 80 or 8080) would wrongly > > exclude all DSpace sites which use HTTPS (port 443). Many institutions > > choose to run DSpace via HTTPS instead of HTTP. > > No problem adding a few more ports to the short list > > > > * Rule #5 (IRs that use the name of the software in the hostname would > > be excluded) may also affect IRs which are hosted by service providers > > (like DSpaceDirect). Again, some DSpaceDirect customers have URLs which > > use *.dspacedirect.org (includes "dspace"). This rule would also exclude > > MIT's IR which is the original "DSpace" (and has used the same URL for > > the last 10+ years): http://dspace.mit.edu/ > > This is easy. Imagine that the people at MIT decide next week they > prefer eprints or other new software. A repository is a repository, > why not a final one like?: > > repository.mit.edu > > On the other side, I wrote all my papers using MS Word and never cited > that fact in any of them, less of all in the authorship > > > > > * Rule #6 (IRs that use more than 4 directory levels for the URL address > > of the full texts will be excluded.) may accidentally exclude a large > > number of DSpace sites. The common download URLs for full text in DSpace > > are both are at least 4 directory levels deep: > > > > - XMLUI: [dspace-url]/bitstream/handle/[prefix]/[id]/[filename] > > - JSPUI: [dspace-url]/bitstream/[prefix]/[id]/[sequence]/[filename] > > > > NOTE: "prefix" and "id" are parts of an Item's Handle > > (http://hdl.handle.net/), which is the persistent identifier assigned to > > the item via the Handle System. So, this is how a persistent URL like > > http://hdl.handle.net/1721.1/26706 redirects to an Item in MIT's DSpace. > > > I understand the technical part, but this for the needs of the > sysadmin of the system (=NE person). Now, please take into account the > needs of 10,000 internal end-users authors. Why
Re: [Dspace-tech] [Dspace-general] Regarding Ranking of Repositories
Dear Anton, Thanks for your different point of view. It is good to opening the debate to further issues. Anton Angelo escribió: > Hi Isidro, > > As a librarian/technologist managing a institutional repository I have to > disagree with you on the definition of our end users. There are two ways > to look at this, and neither end up with the authors as end users. > > An idealistic approach would see the final readers of the items as the end > users. They are the ones, defined by various OA declarations, the ones for > whom we are doing this. Idealistic? It is the current situation. I search for a topic related to my research in Google and I obtain a few hundred results. I focus on the ones coming from the repositories because in most cases that means the full text is openly available. What are the problems? a) Sometimes the repositories results does not appear first, but those from Researchgate or Academia.edu. A few researchers already realizes that and now prefer those portals instead their own institutions for depositing. b) Checking the results some of them are deposited in webserves with suspicious names. I can not recognize trusted reliable university names when that info is not in the URL. c) The paper is in the correct webdomain but from the url I have no hints about if it is a unpublished thesis, a paper in a major journal, authored by a well known colleague or even how recent is it > A pragmatic approach would say the funders of the research are the end > users, as they are demanding the output of their funding to be made OA. For that users it is completely unneeded the huge effort for bulding an open public repository. An annual report of research results is more than enough. > The latter group are the ones your service is most useful for, in > determining the performance of their outputs - the more visible, the better > vehicle for publication. Well, I accept 100 funders. According to the statistics of visits of major repositories we are talking of millions of unique visitor each year. I think there is some misunderstanding about who is really using your (any) repository. > I am beginning to think that rankings are not a very useful manner in which > to compare IRs, but a list of platform agnostic best practice standards > (like the orange book for security, back in the day) is the way forward. Current situation is that most of the world scientific production is not deposited in open access repositories. ANY licit strategy to change that should be welcomed. The ranking is helping, at least pushing managers to convince authors to increase the number of papers deposited. > Though I have extensively used the service in my research on IR > effectiveness, that was mostly because the repository I manage has a high > ranking, and it was useful to promote it internally. Thanks, this is an intended welcomed use of our work This kind of > behaviour usually ends up in 'gaming', and is counterproductive - exactly > what OA is trying to get away from (h-index, impact factor, etc). I know you and the rest of the members of this list are professionals, not gamers. > > IRs are really about getting the right output to the right person - even > one download can be a total success. I think in the future altmetric tools > are probably going to be more use than a ranking service, as useful as it > has been in the past - provided they report on the work in OA being done in > the global south. Do you know that our ranking is including for at least the two last editions altmetrics indicators? Ten of them: Academia, Facebook, LinkedIn, Mendeley, ResearchGate, Slideshare, Twitter, Wikipedia (2) & YouTube. > aa > > > > > > > On 4 September 2014 09:12, Isidro F. Aguillo > wrote: > >> Dear Stuart, >> >> I do not know if you understand the ultimate purpose of Open access >> initiatives in general and the institutional repositories in >> particular. But I think you are mising the central point that the >> end-users should guide the design of the repository according to their >> real needs. >> >> Well, in OA the end users are the authors of the papers, their >> institutions that fund the research and host the papers and the >> librarians who manage the repository. In this scenario the software >> developers task is to fulfill in the most professional way the needs >> of the authors. >> >> Regarding authors needs, the W3C organization and its 'cool' proposals >> is arbitrary basically because they do not know how scholarly >> communication works, and the aims and methods of OA. They are not >> stakeholders for us. >> >> In any case, I will prefer and thank from you comments on the specific >> proposals and not a general, ambigous and unsupported global criticism. >> >> Best regards, >> >> >> Stuart Yeates escribió: >> >> > I'm not sure that knee-jerk reaction to an arbitrary list of bad >> > practice is a good place to start and seems like a reall
Re: [Dspace-tech] [Dspace-general] Regarding Ranking of Repositories
Dear Tim, Tim Donohue escribió: > Hello Isidro, > > DuraSpace (the stewarding organization behind DSpace and Fedora > repository software) was planning to send you a compiled list of the > concerns with your proposal. As you can tell from the previous email > thread, many of the users of DSpace have similar concerns. Rather than > bombard you with all of them individually (which you could see from > browsing the thread), we hoped to draft up a response summarizing the > concerns of the DSpace community. Thanks a lot. That is far beyond my better expectations. > Below you'll find an initial draft of the summarized concerns. The rule > numbering below is based on the numbering at: > http://repositories.webometrics.info/en/node/26 > > --- Concerns with the Proposal from Ranking Web of Repositories > > * Rule #2 (IRs that don't use the institutional domain will be excluded) > would cause the exclusion of some IRs which are hosted by DSpace service > providers. As an example, some DSpaceDirect.org users have URLs > https://[something].dspacedirect.org which would cause their exclusion > as it is a non-institutional domain. Many other DSpace hosting providers > have similar non-institutional domain URLs by default. Major issue. Repository is not another bibliographic database, it is the archive of the academic output of the institution. And as such it should be iron brand. If .. the institution is very small or in a country with limited resources the hosting option is perfectly valid and we will do an exception. But in these cases, Is not a redirection possible? If .. the problem is related to governance we should not reward the institution bad practice. > * Rule #4 (Repositories using ports other than 80 or 8080) would wrongly > exclude all DSpace sites which use HTTPS (port 443). Many institutions > choose to run DSpace via HTTPS instead of HTTP. No problem adding a few more ports to the short list > * Rule #5 (IRs that use the name of the software in the hostname would > be excluded) may also affect IRs which are hosted by service providers > (like DSpaceDirect). Again, some DSpaceDirect customers have URLs which > use *.dspacedirect.org (includes "dspace"). This rule would also exclude > MIT's IR which is the original "DSpace" (and has used the same URL for > the last 10+ years): http://dspace.mit.edu/ This is easy. Imagine that the people at MIT decide next week they prefer eprints or other new software. A repository is a repository, why not a final one like?: repository.mit.edu On the other side, I wrote all my papers using MS Word and never cited that fact in any of them, less of all in the authorship > * Rule #6 (IRs that use more than 4 directory levels for the URL address > of the full texts will be excluded.) may accidentally exclude a large > number of DSpace sites. The common download URLs for full text in DSpace > are both are at least 4 directory levels deep: > > - XMLUI: [dspace-url]/bitstream/handle/[prefix]/[id]/[filename] > - JSPUI: [dspace-url]/bitstream/[prefix]/[id]/[sequence]/[filename] > > NOTE: "prefix" and "id" are parts of an Item's Handle > (http://hdl.handle.net/), which is the persistent identifier assigned to > the item via the Handle System. So, this is how a persistent URL like > http://hdl.handle.net/1721.1/26706 redirects to an Item in MIT's DSpace. I understand the technical part, but this for the needs of the sysadmin of the system (=NE person). Now, please take into account the needs of 10,000 internal end-users authors. Why not redirect (aliasing?)? > * Rule #7 (IRs that use more than 3 different numeric (or useless) codes > in their URLs will be excluded.). It is unclear how they would determine > this, and what the effect may be on DSpace sites worldwide. Again, > looking at the common DSpace URL paths above, if a file had a "numeric" > name, it may be excluded as DSpace URLs already include 2-3 numeric > codes by default ([prefix],[id], and [sequence] are all numeric). I have a personal example. 20 years ago my email admin decided my email account should be 'dctfa11', abusing from your notation ([prefix],[id], and [sequence]). After several years it was possible to change to 'isidro.aguillo'. I going to use the URL of my papers to cite them, to marketing them, to copy in my CV, . Please, help me translating /56/89/567894 into aguillo2014b > * Rule #8 (IRs with more than 50% of the records not linking to OA full > text versions..). Again, unclear how they would determine this, and > whether the way they are doing so would accidentally exclude some major > DSpace sites. For example, there are major DSpace sites which include a > larger number of Theses/Dissertations. These Theses/Dissertations may > not be 100% Open Access to the world, but may be fully accessible > everyone "on campus". 50%!!! A 'place' with less than 50% of the full texts unavailable is NOT an Open Access Repository. > Another
Re: [Dspace-tech] Request a copy
Thanks for all the replies on this issue everybody!
Helpful as always!
Cheers,
Gary
GARY BROWNE | Development Programmer
Library IT Services | Fisher Library F03
THE UNIVERSITY OF SYDNEY
T +61 2 9351 5946 | M +61 405 647 868
E gary.bro...@sydney.edu.au | W http://sydney.edu.au
Sent from my plain old desktop computer.
CRICOS 00026A
This email plus any attachments to it are confidential. Any unauthorised use is
strictly prohibited. If you receive this email in error, please delete it and
any attachments.
Please think of our environment and only print this e-mail if necessary.
> -Original Message-
> From: Michael White [mailto:michael.wh...@stir.ac.uk]
> Sent: Tuesday, 2 September 2014 8:46 PM
> To: Gary Browne
> Cc: dspace-tech@lists.sourceforge.net
> Subject: RE: [Dspace-tech] Request a copy
>
> Hi Gary,
>
> > Is it possible to have the "Request a copy" button send to a DSpace
> > administrator email address only, rather than to the item owner? If
> > so, where would I configure/code/hack this?
>
> I've done something similar with our DSpace v4.1/JSPUI - Amongst other
> changes to our Embargo/Request a copy handling, I hacked our "Request a
> copy" implementation to send the Request email to an email address
> specified in the item's metadata (rather than always sending to the
> submitter), and I added a config option to dspace.cfg to specify the metadata
> field that held that address (which is "dc.author.email" in our case).
>
> To achieve this, I hacked "RequestItemServlet.java" (src in /usr/src/dspace-
> 4.1-src-release/dspace-jspui/src/main/java/org/dspace/app/webui/servlet
> IIRC), and I've attached my hacked version in case it is of use or help to you
> (I'm guessing the mailing list will strip this, though, so if anyone else is
> interested in this, just let me know). If you search for "MW" in this file,
> you'll
> see the places where I've added/hacked the code (all my hacks (should!)
> have comments with my initials and the date) . . .
>
> Basically, if you want to control where the email goes, I think you need to
> affect the email address that is passed into this line (it was a while ago I
> did
> this!):
>
> email.addRecipient(emailRequest);
>
> - which occurs in the processForm and processAdmin functions I think . . .
>
> So, if you wanted to hard code it, you could simply put the email address in
> there (probably pulled from the config using
> ConfigurationManager.getProperty("mail.admin") rather hard coding the
> actual address) . . .
>
> Alternatively, I note that just above the "addRecipient" line, the code checks
> if emailRequest is empty, and if it is, populates it with the Admin email
> address instead (I THINK this is in the original, and isn't something I have
> added!?):
>
> if (emailRequest == null) {
> emailRequest = ConfigurationManager
> .getProperty("mail.admin");
> }
>
> So, you could hack this test to get the change you want?
>
> If it were me, I'd probably add a flag to the config file (a key with a value
> of
> true or false) and add a test for that value to the if statement above, that
> way you could toggle between sending emails to the Admin or to the
> "expected" email address simply by changing the config option - so, for
> example (off the top of my head, and NOT TESTED!), in dspace.cfg, add:
>
> request.item.adminemail = true
>
> - and then hack the above to something like:
>
> if ((emailRequest == null) ||
>
> ("true".equalsIgnoreCase(ConfigurationManager.getProperty("requ
> est.item.adminemail "))) {
> emailRequest = ConfigurationManager
> .getProperty("mail.admin");
> }
>
> [Not sure if you actually need to test against "true", or if the value in
> "request.item.adminemail" can be used as a Boolean "as is" (without a
> comparison) - so you may be able to clean that up a little!]
>
> The above may not be the best way to achieve what you want (and others
> are welcome to correct me or offer other/better solutions!), but would
> probably get you where you want to go!
>
> I hope this is of some use.
>
> Regards,
>
> Mike
>
> Michael White
> eLearning Liaison and Development (eLD)
> Information Services
> S8, Library
> University of Stirling
> Stirling SCOTLAND
> FK9 4LA
> Email: michael.wh...@stir.ac.uk
> Tel: +44 (0) 1786 466877
> Fax: +44 (0) 1786 466880
> http://www.stir.ac.uk/is/staff/about/teams/aldt/#eld
>
> >
> > Message: 5
> > Date: Tue, 2 Sep 2014 06:58:59 +
> > From: Gary Browne
> > Subject: [Dspace-tech] Request a copy
> > To: dspace-tech Tech
> > Message-ID: <23DF3A1C5648DD43BCAE0666B5AFAD119405096A@ex-mbx-
> > pro-02>
> > Content-Type: text/plain; charset="iso-8859-1"
> >
> > Hi all,
> >
> > DSpace version: 4.1
> > UI: JSP
> > Servlet container: Tomcat 7
> > Server: RHEL 6.5 64-bit
> > Java: OpenJDK 1.7
> >
> >
Re: [Dspace-tech] [Dspace-general] Regarding Ranking of Repositories
Dear Kim, Thanks for your message. I answer to your specific comments Kim Shepherd escribió: > Hi Isidro and lists, > > Regarding point 6 -- I see what you're saying, but it shouldn't really be > up to the DSpace community repositories (who all use the handle prefix / > identifier system, as I'm sure you know!) to argue why 1234/123 is better > than thesis/phsyics/something, because we're not the ones proposing that > URI segments be part of any metric used to judge the "world ranking" of a > repository. It's also not as simple as you might think, particularly when > ensuring unique URIs and persistent URIs, etc. > I think you're saying that URIs should either "look nice" or "be > meaningful", or both, but I'm not sure we should rely on URIs to be too > meaningful, especially when we have ways of including that with semantic > markup in references, structured data in our METS/ORE feeds via OAI, etc. This is the basic misunderstanding. The repository end user is an author that whishes to increase the global visibility and usage of his/her deposited papers. Looking nice is relevant because the main tool of the author for obtaining visibility and visits is to cite them in his/her future papers or to mention it for example in Wikipedia or Twitter. Looking nice is adding informative value (authors name, publication year, topic) that can be relevant for the reader helping to decide if following the link. Looking nice also works as quality control, a mistake in lastname is easier to notice that in a series of numbers. But far more importat: By far the largest number of visitors came from Google or other engines. If you are not searching for specific title, then the semantic content of the URL is increasing considerably your positioning in Google. Of course, you can ignore that, but there is already many people who prefers to deposit in ResearchGate or Academia as the visibility of their works is better. > > Regarding point 5 -- I don't see that this matters either. No end user > cares what the IR is actually called, surely? Whatever arguments you can > make for our IRs having "bad names", punishing us for preserving the > permanence of those names and URIs we've already minted seems a bit unfair? > The first IR I thought of when reading this was, of course, > http://dspace.mit.edu. > I think point 5 actually punishes EPrints repositories most unfairly, since > "eprints" is an accepted name for digital manuscripts as well as the > platform used -- I think I've even seen IRs called "eprints.something.etc" > running platforms other than EPrints. You are answering the question. Imagine that in the future I decide to use eprints instead of dspace or whatever other better that can be developed in the future. Then, are going to change the domain or not?. On the other side, why branding an intellectual result with the name of the tool?. I write my papers with MS Word and never made any significant mention of this fact in any of the papers. What is the problem with? http://repository.university.edu/ > > Numbers 6 and 7, I think I agree with Mark, but don't really have anything > to add. I don't really understand why this would even be considered as a > metric, let alone grounds for exclusion. What are some examples of cases > where long URIs (or, eg. "directories as fulltext" hosted in IRs with their > own dir structures, which happens) or URIs which happen to contain numbers > result in end users or machines not being able to properly locate/use > hosted resources? Metrics? Who is talking about metrics? I only said Keep It Simple. > Number 8 is probably the thing that will punish my own institution most, > which is a pity because we have a large absolute amount of fulltext, but > for various reasons, a lot of record only items as well. This is probably a > philisophical argument about defining an "OA repository" I guess? We can discuss about the threshold, I think 50% is reasonably but it could be used only for contents after embargo ends (usually 6 or 12 months). > I hope my criticisms here don't seem too harsh - thanks for taking the time > to listen to feedback. > > On a lighter note, I'm sort of pleased these proposals have been doing the > rounds, as I think it might just be the thing that convinces my own > institution to take "world repository ranking" off our KPIs, and > concentrate more on qualitative value of the repository we host. Thanks for your cooperation ... > Cheers > > Kim (a DSpace dev/admin, and already biased against quantitative metrics in > IRs so not exactly an objective commenter ;)) You are a perfect objective commenter as you identify as dev/admin but the repository was not intended to serve you. The 'customers' are your authors and your institution and THEY are strongly biased to support metrics. Simply, ask them. > > On 3 September 2014 07:56, Isidro F. Aguillo > wrote: > >> Dear colleagues, >> >> As editor of the Ranking W
Re: [Dspace-tech] [Dspace-general] Regarding Ranking of Repositories
Dear Stuart, I do not know if you understand the ultimate purpose of Open access initiatives in general and the institutional repositories in particular. But I think you are mising the central point that the end-users should guide the design of the repository according to their real needs. Well, in OA the end users are the authors of the papers, their institutions that fund the research and host the papers and the librarians who manage the repository. In this scenario the software developers task is to fulfill in the most professional way the needs of the authors. Regarding authors needs, the W3C organization and its 'cool' proposals is arbitrary basically because they do not know how scholarly communication works, and the aims and methods of OA. They are not stakeholders for us. In any case, I will prefer and thank from you comments on the specific proposals and not a general, ambigous and unsupported global criticism. Best regards, Stuart Yeates escribió: > I'm not sure that knee-jerk reaction to an arbitrary list of bad > practice is a good place to start and seems like a really bad driver > for software development. > > Maybe we should be talking to our fellow implementers and building > on the work of http://www.w3.org/Provider/Style/URI.html, > http://www.w3.org/TR/cooluris/, > http://www.openarchives.org/OAI/openarchivesprotocol.html, etc. to > build a compilation of _best_ practice. > > Cheers > stuart > > -Original Message- > From: Tim Donohue [mailto:tdono...@duraspace.org] > Sent: Wednesday, 3 September 2014 8:49 a.m. > To: Isidro F. Aguillo; dspace-tech@lists.sourceforge.net > Cc: Jonathan Markow; dspace-gene...@lists.sourceforge.net > Subject: Re: [Dspace-general] [Dspace-tech] Regarding Ranking of Repositories > > Hello Isidro, > > DuraSpace (the stewarding organization behind DSpace and Fedora > repository software) was planning to send you a compiled list of the > concerns with your proposal. As you can tell from the previous email > thread, many of the users of DSpace have similar concerns. Rather > than bombard you with all of them individually (which you could see > from browsing the thread), we hoped to draft up a response > summarizing the concerns of the DSpace community. > > Below you'll find an initial draft of the summarized concerns. The > rule numbering below is based on the numbering at: > http://repositories.webometrics.info/en/node/26 > > --- Concerns with the Proposal from Ranking Web of Repositories > > * Rule #2 (IRs that don't use the institutional domain will be > excluded) would cause the exclusion of some IRs which are hosted by > DSpace service providers. As an example, some DSpaceDirect.org users > have URLs https://[something].dspacedirect.org which would cause > their exclusion as it is a non-institutional domain. Many other > DSpace hosting providers have similar non-institutional domain URLs > by default. > > * Rule #4 (Repositories using ports other than 80 or 8080) would > wrongly exclude all DSpace sites which use HTTPS (port 443). Many > institutions choose to run DSpace via HTTPS instead of HTTP. > > * Rule #5 (IRs that use the name of the software in the hostname > would be excluded) may also affect IRs which are hosted by service > providers (like DSpaceDirect). Again, some DSpaceDirect customers > have URLs which use *.dspacedirect.org (includes "dspace"). This > rule would also exclude MIT's IR which is the original "DSpace" (and > has used the same URL for the last 10+ years): http://dspace.mit.edu/ > > * Rule #6 (IRs that use more than 4 directory levels for the URL > address of the full texts will be excluded.) may accidentally > exclude a large number of DSpace sites. The common download URLs for > full text in DSpace are both are at least 4 directory levels deep: > > - XMLUI: [dspace-url]/bitstream/handle/[prefix]/[id]/[filename] > - JSPUI: [dspace-url]/bitstream/[prefix]/[id]/[sequence]/[filename] > > NOTE: "prefix" and "id" are parts of an Item's Handle > (http://hdl.handle.net/), which is the persistent identifier > assigned to the item via the Handle System. So, this is how a > persistent URL like > http://hdl.handle.net/1721.1/26706 redirects to an Item in MIT's DSpace. > > * Rule #7 (IRs that use more than 3 different numeric (or useless) > codes in their URLs will be excluded.). It is unclear how they would > determine this, and what the effect may be on DSpace sites > worldwide. Again, looking at the common DSpace URL paths above, if a > file had a "numeric" > name, it may be excluded as DSpace URLs already include 2-3 numeric > codes by default ([prefix],[id], and [sequence] are all numeric). > > * Rule #8 (IRs with more than 50% of the records not linking to OA > full text versions..). Again, unclear how they would determine this, > and whether the way they are doing so would accidentally exclude > some major DSpa
Re: [Dspace-tech] DSPACE: (discovery) Is it possible to show a specific sidebarFacets for a specific collection?
Your approach should work. After making the change, did you restart DSpace and rebuild your discovery index? Once you are able to see the new facets, you will also need to update your messages.xml with the name of your facet. Terry On Wed, Sep 3, 2014 at 11:49 AM, Johanne Crête wrote: > I am using DSpace 4.1 and I want to show a specific sidebarFacets for a > specific collection. I try to do this by adding a new > "org.dspace.discovery.configuration.DiscoveryConfiguration" in > discovery.xml. And a new entry key for the specific collection. But, I > don't see this sidebarFacets. There is another solution to do this? > > > > DISCOVERY.XML > > -- > > id="org.dspace.discovery.configuration.DiscoveryConfigurationService" > class="org.dspace.discovery.configuration.DiscoveryConfigurationService"> > > > > > > > > > > > > > > > > > > > > > > …. > > > > class="org.dspace.discovery.configuration.DiscoveryConfiguration" > scope="prototype"> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > …. > > > > class="org.dspace.discovery.configuration.DiscoverySearchFilterFacet"> > > > > > > > > dc.description.journal > > > > > > > > > > > > > > ... > > > > > > > > > > > -- > Slashdot TV. > Video for Nerds. Stuff that matters. > http://tv.slashdot.org/ > ___ > DSpace-tech mailing list > DSpace-tech@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dspace-tech > List Etiquette: > https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette > -- Terry Brady Applications Programmer Analyst Georgetown University Library Information Technology https://www.library.georgetown.edu/lit/code 425-298-5498 -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
[Dspace-tech] DSPACE: (discovery) Is it possible to show a specific sidebarFacets for a specific collection?
I am using DSpace 4.1 and I want to show a specific sidebarFacets for a specific collection. I try to do this by adding a new "org.dspace.discovery.configuration.DiscoveryConfiguration" in discovery.xml. And a new entry key for the specific collection. But, I don't see this sidebarFacets. There is another solution to do this? DISCOVERY.XML -- dc.description.journal ... -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
[Dspace-tech] Mirage2 Error
Hi all! Using DSpace 4.2 with the new Mirage2 theme, I am seeing a javascript error: Unknown template object: function at handlebars.js line 455 and line 644 seemingly with no ill effects, but I'd like to track down the source of the problem and get rid of it! Any ideas? Thanks, Bill -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] Dspace 3.1 to 4.2 upgrade: XMLUI webapp not running and can not be started
Hi, I just wanted to let you know that I have now successfully upgraded the Dspace on my dev. The problem was actually to do with @mire cua module which was being referenced in spring configs but whose jar files are not deployed for now. Thank you so much for your help. Best Nason On 2 September 2014 15:44, Nason Bimbe wrote: > Thanks for this, will try it out. > > > On 2 September 2014 15:43, Pottinger, Hardy J. > wrote: > >> Hi, Nason, here is the init script I use for running a binary install >> of Tomcat 7 on RHEL [1] Note that it gets progressively more aggressive >> when shutting down Tomcat. This script is a "mash-up" of a few sample >> Tomcat init scripts I found online, citations are given in the code. >> >> [1] https://gist.github.com/hardyoyo/9903387 >> >> >> *From:* Nason Bimbe [nasonbi...@gmail.com] >> *Sent:* Tuesday, September 02, 2014 9:25 AM >> *To:* Pottinger, Hardy J. >> *Cc:* Peter Dietz; dspace-tech >> *Subject:* Re: [Dspace-tech] Dspace 3.1 to 4.2 upgrade: XMLUI webapp not >> running and can not be started >> >> Hi Hardy, >> I will be trying it out again tomorrow afresh after restoring the system >> to before the attempted upgrade. I am using a script I created in >> /etc/init.d for starting/stopping Tomcat. I will also try Shaun Donovan's >> information which he sent directly to me and shown below. I will update you >> how it on progress. Thanks again for the help. >> >> Best >> Nason >> >> I had this problem, not on xmlui but on oai. I found the following on >> the web and tried it, and it worked. >> >> Check Inside the Following Directory for the jar file el-api.jar >> :C:\apache-tomcat-7.0.39\lib\el-api.jar if it exists then in this >> directory of your web application WEB-INF\lib\el-api.jar the jar >> should be removed >> >> What I did is find the file, and moved it, then the app started without >> issues. This was on a development machine. I then tried it on the >> production machine and my oai would still not start. I had other issues in >> my catalina.out which pointed to the web.xml file in tomcats conf directory >> which had Slashdot TV. > Video for Nerds. Stuff that matters. > http://tv.slashdot.org/ > ___ > DSpace-tech mailing list > DSpace-tech@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dspace-tech > List Etiquette: > https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette > >>> >> > -- Slashdot TV. Video for Nerds. Stuff that matters. http://tv.slashdot.org/___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] JSPUI reverse proxy authentication
Hi,
does the dspace.log log file contains any entries like the following one?
2014-MM-DD HH:MM:SS,YYY WARN org.dspace.app.webui.util.UIUtil @ POSSIBLE
HIJACKED SESSION: request from XXX.XXX.XXX.XXX does not match original session
address: XXX.XXX.XXX.XXX. Authentication rejected.
How are the configuration properties dspace.baseUrl and dspace.url set?
Regards,
Pascal Becker
From: Fitzpatrick, Christopher [mailto:c...@wmu.se]
Sent: Wednesday, September 03, 2014 9:37 AM
To: dspace-tech@lists.sourceforge.net
Subject: [Dspace-tech] JSPUI reverse proxy authentication
Hi All,
I just setup dspace for the first time. We're wanting to use the jspui
interface. I setup nginx as a reverse proxy in front of tomcat, but it seems
that the authentication is not sticking. What I mean by that is I can
authenticate a user, and the page does show that I am logged in ( and I have
access to certain restricted pages). But the user will lose its session after a
couple of minutes or on certain pages.
This is not happening if I access tomcat directly at port 8080, so I think
there's something I'm missing on my nginx conf. ( included below ).
Any ideas? Thanks for the help...b,chris,
location / {
proxy_pass http://dspace;
proxy_next_upstream error timeout invalid_header http_500 http_502
http_503 http_504;
proxy_redirect http://dspace http://dlib.wmu.se;
proxy_buffering off;
proxy_store off;
proxy_connect_timeout 120;
proxy_send_timeout120;
proxy_read_timeout120;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Server $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
--
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] OAI baseURL "incorrect" . . .
Hi again,
> So, does anyone have any thoughts on where this reference to localhost
> could be creeping in? Is the "baseURL" taken from config somewhere
> (where?), or assumed from the URL used to access the OAI interface (which
> Apache may be mangling)?
Just for the record/mail archives - I looked into this in a bit more depth, and
it looked to me from examining the code in DSpaceIdentify.java that the OAI
baseURL is indeed determined by picking apart the request URL rather than
pulling it from config:
public String getBaseUrl()
{
if (_baseUrl == null)
{
_baseUrl = _request.getRequestURL().toString()
.replace(_request.getPathInfo(), "");
}
return _baseUrl + _request.getPathInfo();
}
- so if the hostname of the request URL that was being picked apart was
"localhost:8080", this did point to an issue with the request that Apache was
passing on to Tomcat . . .
Once I'd convinced myself of that fact and conveyed all that to my sys admin
colleague, he hacked about with the Apache and connector configurations (we're
using mod_proxy I believe) and we finally got it working, so the OAI base URL
that appears in the Identify response for our repository is now correct :-).
Cheers,
Mike
Michael White
eLearning Liaison and Development (eLD)
Information Services
S8, Library
University of Stirling
Stirling SCOTLAND
FK9 4LA
Email: michael.wh...@stir.ac.uk
Tel: +44 (0) 1786 466877
Fax: +44 (0) 1786 466880
http://www.stir.ac.uk/is/staff/about/teams/aldt/#eld
> -Original Message-
> From: Michael White
> Sent: 02 September 2014 15:14
> To: dspace-tech@lists.sourceforge.net
> Subject: OAI baseURL "incorrect" . . .
>
> Hi,
>
> I was just checking the OAI-PMH output of my new DSpace v4.1 PROD system
> against the OAI-PMH validator and was surprised to find the validation had
> failed due to a "baseURL mismatch", even though it had all been lovely when I
> tested it previously on my DEV system.
>
> [FAIL] baseURL supplied 'http://dspace.stir.ac.uk/oai/request' does not match
> the baseURL in the Identify response 'http://localhost:8080/oai/request'.
>
> - and they are quite right (obviously!) - when accessing
> http://dspace.stir.ac.uk/oai/request?verb=Identify, I see :
>
> http://localhost:8080/oai/request
>
> STORRE
> http://localhost:8080/oai/request
> ...
>
> But this all looks OK in my DEV system
> (http://dspace4dev.stir.ac.uk:8080/oai/request?verb=Identify):
>
> verb="Identify">http://dspace4dev.stir.ac.uk:8080/oai/request
>
> STORRE (v4 DEV)
> http://dspace4dev.stir.ac.uk:8080/oai/request
>
> I've checked through the various config files, and I can't see any difference
> (or any unexpected references to localhost) - the main difference between
> the systems is that I'm going straight to Tomcat on port 8080 in my DEV
> environment and my sys admin colleague has stuck Apache in front of Tomcat
> for our PROD system - I'll also add that, in order to validate our DEV system,
> my sys admin colleague installed the reverse proxy "pound" so that we could
> make the DEV system visible from off campus on port 80, and the OAI-PMH
> output of my DEV system also validated correctly through that route.
>
> I've tried clearing the OAI cache and rebuilding the index, but no joy so far
> . . .
>
> I also did a search for "localhost" in all the config files to see if I could
> see
> where this might be creeping in, but, again, no joy . . .
>
> So, does anyone have any thoughts on where this reference to localhost
> could be creeping in? Is the "baseURL" taken from config somewhere
> (where?), or assumed from the URL used to access the OAI interface (which
> Apache may be mangling)? Any suggestions of anything else to
> change/investigate?
>
> Given this works OK in DEV and the configs appear to be the same (or
> equivalent) in all the key places (as far as I can tell), I'm wondering if
> Apache is
> to blame for this? But I'd obviously like to eliminate DSpace config as a
> suspect
> before I go back to my sys admin colleague . . .
>
> Any thoughts, insights or pointers would be welcome :-)
>
> Cheers,
>
> Mike
>
> Michael White
> eLearning Liaison and Development (eLD)
> Information Services
> S8, Library
> University of Stirling
> Stirling SCOTLAND
> FK9 4LA
> Email: michael.wh...@stir.ac.uk
> Tel: +44 (0) 1786 466877
> Fax: +44 (0) 1786 466880
> http://www.stir.ac.uk/is/staff/about/teams/aldt/#eld
>
--
The University of Stirling has been ranked in the top 12 of UK universities for
graduate employment*.
94% of our 2012 graduates were in work and/or further study within six months
of graduation.
*The Telegraph
The University of Stirling is a charity registered in Scotland, number SC
011159.
--
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
[Dspace-tech] JSPUI reverse proxy authentication
Hi All,
I just setup dspace for the first time. We're wanting to use the jspui
interface. I setup nginx as a reverse proxy in front of tomcat, but it
seems that the authentication is not sticking. What I mean by that is I can
authenticate a user, and the page does show that I am logged in ( and I
have access to certain restricted pages). But the user will lose its
session after a couple of minutes or on certain pages.
This is not happening if I access tomcat directly at port 8080, so I think
there's something I'm missing on my nginx conf. ( included below ).
Any ideas? Thanks for the help...b,chris,
location / {
proxy_pass http://dspace;
proxy_next_upstream error timeout invalid_header http_500 http_502
http_503 http_504;
proxy_redirect http://dspace http://dlib.wmu.se;
proxy_buffering off;
proxy_store off;
proxy_connect_timeout 120;
proxy_send_timeout120;
proxy_read_timeout120;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Server $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
--
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
