[Dspace-general] DSpace 1.6.0 RC2 is released!

2010-02-11 Thread Tim Donohue
All,

DSpace 1.6.0 Release Candidate 2 (RC2) is now officially released.

You may download it from either of the following locations:

* SourceForge: https://sourceforge.net/projects/dspace/files/
* Subversion: http://scm.dspace.org/svn/repo/dspace/tags/dspace-1.6.0-rc2/

As mentioned in my previous email (see below) we are hosting a second 
Testathon next week, Feb. 15-19, 2010.  The goal of this Testathon is to 
ensure 1.6.0 RC2 is fully stable and all bugs from RC1 have been resolved.

More information will be forthcoming on our 1.6.0 Testathon page:
http://wiki.dspace.org/index.php/Testathon

I'd again encourage you to help us test this release next week (or even 
earlier if you want to install it yourself).

Thanks again!

Tim

On 2/9/2010 10:21 AM, Tim Donohue wrote:
 All,

 We have a few big announcements regarding 1.6.0 this week!

 *1.6.0 RC2 Release*

 Later this week, we will be making DSpace 1.6.0 Release Candidate 2
 (RC2) publicly available. An official announcement will be sent out once
 it is available for download (likely Weds evening / Thurs morning).

 DSpace 1.6.0 RC2 resolves bugs/issues that were found in the 1.6.0 RC1
 release (back in December). The DSpace developers feel that this RC2
 release is much more stable and much closer to a final 1.6.0 release.

 *1.6.0 RC2 Testathon: Feb 15-19, 2010*

 However, to ensure we've located and fixed all the major bugs, we'll be
 having a second Testathon next week (Feb 15-19, 2010). As in December,
 several members of the DSpace community will host public instances of
 1.6.0 RC2 for you to sign onto and put 1.6 through its paces. You will
 also be able to download the latest RC2 release locally to perform a
 test installation or test upgrade.

 More information will be forthcoming on our 1.6.0 Testathon page:
 http://wiki.dspace.org/index.php/Testathon

 Again, we'd encourage anyone and everyone to help in the Testathon. Any
 time you can provide (even just 10-15 minutes) can help us ensure that
 DSpace 1.6.0 is one of the best releases yet!

 *Upcoming Release Schedule*

 As I mentioned, the DSpace Developers believe that things are much more
 stable in 1.6.0 RC2. Assuming the bugs are minor or minimal in next
 week's Testathon, we feel that we're only a few weeks away from the
 1.6.0 final release. Here's our revised release schedule:

 * Feb 10/11: Release 1.6.0 RC2
 * Feb 15-19: Testathon of 1.6.0 RC2
 * Feb 22-26: Resolve any issues from Testathon (hopefully all minor)
 * March 1: Release 1.6.0 Final

 Again, the above release schedule is tentative and is based on the
 results of the 1.6.0 RC2 Testathon. However, we feel confident that
 1.6.0 will finally be in your hands at the beginning of March.

 Thanks in advance for all your help! We are all excited to finally be in
 the home stretch for 1.6.0!

 Tim Donohue
 Technical Lead for DSpace Project
 DuraSpace.org

--
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] Reminder: DSpace 1.6 Testathon all week long

2010-02-15 Thread Tim Donohue
All,

Just a reminder, all week long (Feb 15-19) we are running our second 
DSpace 1.6 Testathon - The Big Bug Hunt.  We have three DSpace 
1.6.0-RC2 test instances up and running.  Please try to take some time 
out of your week to help us test!  We can use help from repository 
managers, developers, or just interested users.  More information about 
the Testathon is available at:
http://wiki.dspace.org/index.php/Testathon

If you find what you think is a bug, feel free to report it in our 
DSpace Jira (http://jira.dspace.org).   If you want to confirm it first, 
we have DSpace developers available to talk in our DSpace IRC chat room. 
  The easiest way to join our chat room is to visit our Testathon 
website at  http://dspace.testathon.net/  (Then, just enter in a 
nickname of your choice and click Login).   If you are new to online 
chat, don't worry, we're all very friendly!  Feel free to introduce 
yourself when you join the room, and let us know if you've found 
anything in your testing.

*Upcoming Release Schedule*

As we've mentioned previously, the DSpace Developers believe that things 
are much more stable in 1.6.0 RC2.  Assuming the bugs are minor or 
minimal in this week's Testathon, we feel that we're only a few weeks 
away from the 1.6.0 final release.  Here's our current planned schedule:

* Feb 15-19: Testathon for 1.6.0 RC2
* Feb 22-26: Resolve any issues from Testathon (hopefully all minor)
* March 1 or 2: Release 1.6.0 Final

So, if you can find some time this week, please help us make DSpace 1.6 
one of the best releases yet!

Thanks again for your help,

Tim Donohue
Technical Lead for DSpace
DuraSpace.org

--
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] Call for new DSpace Committer nominations

2010-03-03 Thread Tim Donohue
All,

The DSpace Committers group would like to extend a general call to the 
DSpace Community for nominations of individuals to add to our Committers 
group.  New Committers may be nominated by anyone in the Community at 
any time.


* Roles and Duties of a Committer *

Being a committer means participating in the evolution of the DSpace 
platform, typically by making changes to the source code, improving 
documentation, or managing the integration of contributions made by the 
community at large. But, it also means having a voice and an official 
vote on technical, administrative and release management issues, 
providing your expertise and guidance on the lists, organizing testing, etc.

We are mindful of the fact that no one is being paid to do this, and no 
specific time commitment is required or expected; in fact we *do* expect 
that one's involvement will fluctuate over time with job duties. Nor is 
there any specified term of office - one's job responsibilities may 
change over time, and also one's ability to devote time to DSpace.


* Why Become a Committer? *

Becoming a committer means that you have a voice and an official vote on 
decisions around the evolution of the DSpace platform.  It also gives 
you an opportunity to develop leadership skills in an friendly, open 
source community.


* Committer Requirements *

Although there are no explicit requirements to become a committer, 
generally we look for someone who has shown initiative and/or has been 
an active participant in the DSpace Community.  Participation may be in 
the form of actively helping people on mailing lists, submitting code 
patches/features, presenting on DSpace at conferences, leading 
workshops, or generally volunteering time to help with any DSpace 
initiative.

It's worth noting that committers need not be highly technical in 
nature.  We only ask that you make a commitment to bettering DSpace in 
some way.  Anyone who shows the initiative and interest in making DSpace 
better is eligible.


* How to Nominate Someone *

New committers may be nominated by anyone in the DSpace Community at any 
time.  You can even nominate yourself.

In your nomination, please explain why you feel this individual (or 
individuals) should be added to the Committers group.  Generally, we are 
just looking for references to his/her active participation in the 
DSpace Community.

Send new committer nominations to DSpace Tech Lead, Tim Donohue 
(tdono...@duraspace.org), or any of the existing DSpace Committers.  A 
current listing of Committers can be found on our wiki:
http://wiki.dspace.org/index.php/DSpaceContributors

Again, there is no specific timeline for nominations.  Nominations may 
be made at any time.

If you have any questions, feel free to ask!

Sincerely,

The DSpace Committers Group

--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] Introducing three new DSpace Committers!

2010-03-19 Thread Tim Donohue
All,

On behalf of the DSpace Committers Group, I'd like to formally welcome 
Peter Dietz, Robin Taylor, and Keith Gilbertson to our team. These three 
individuals were nominated by three different members of our DSpace 
Community.  All have shown great initiative in volunteering their time 
to help out DSpace Software and our DSpace Community.

Peter Dietz is the Systems Developer / Engineer for Ohio State 
University's DSpace instance, The Knowledge Bank 
(https://kb.osu.edu/dspace/). Peter is a recent addition to our DSpace 
community, but he has jumped straight in and has been actively assisting 
the DSpace Community in #dspace IRC, JIRA and our mailing lists.  He was 
also instrumental in helping to test/debug the new DSpace 1.6 Statistics 
engine (especially its ability to load large amounts of data from 
existing dspace log files) during the most recent Testathons.

Robin Taylor is a developer at the Edinburgh University Library, where 
his primary role is to maintain and develop their various installations 
of DSpace.  This includes not only the Edinburgh University Library's 
Edinburgh Research Archive (http://www.era.lib.ed.ac.uk/), but also a 
number of other DSpace installations for partners within the Scottish 
Digital Library consortium (http://www.nls.uk/sdlc/).  Robin has been 
active within the DSpace community for several years now, helping out on 
mailing lists, providing bug reports / patches, and helping to ask some 
tricky questions.  He was also instrumental in developing a new Item 
type-based Submission module for DSpace (one that we are hopeful will be 
formally released in a future version of DSpace): 
http://jira.dspace.org/jira/browse/DS-464

Keith Gilbertson is the technical lead for the Georgia Institute of 
Technology's GALILEO Knowledge Repository (http://tinyurl.com/yz9v79x), 
based on DSpace technology and sponsored by the Institute of Museum and 
Library Services (IMLS).  Previous to this position, Keith assisted in 
the construction of OhioLINK's DSpace-based Digital Resource Commons 
project (http://drc.ohiolink.edu).  Since 2007, Keith has been actively 
helping out on mailing lists and providing bug reports / patches to 
DSpace.  Most recently, he was also a very active participant in both of 
our 1.6 Testathons.

Please join us in congratulating and welcoming our three new DSpace 
Committers!

Sincerely,

The DSpace Committers Group.


-- 
Tim Donohue
Technical Lead for DSpace Project
DuraSpace.org

--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] Why can't the submitter remove bistreams?

2010-05-03 Thread Tim Donohue
Hi Fang  Dorothea,

On 5/3/2010 10:10 AM, Dorothea Salo wrote:
 On Mon, May 3, 2010 at 10:05 AM, Wang, Fangfang.w...@ttu.edu  wrote:
 Thanks, Dorothea. But that sounds insane!! I find the permissions in Dspace 
 especially frustrating/not user-friendly!

 So do I; I've been complaining about them for nearly five years.
 Perhaps you'll have better luck motivating action than I have.

Dorothea's previous statement about Administrator-only deletion of 
bitstreams is not entirely accurate (at least not for DSpace 1.6.0).

In DSpace 1.6, we now have Delegated Administration options, which by 
default allow Administrators, Community Administrators or Collection 
Administrators to delete/replace bitstreams on items.

There is also a new concept of an Item Administrator which comes with 
this Delegated Administration option. Item Administrators also have 
the ability to delete/replace bitstreams on items by default.

By default, in 1.6.0, Submitters are NOT made into Item Administrators, 
but you could add code to enable this functionality. Perhaps in a future 
version of DSpace we could make this more of a configuration option 
available to institutions.

If you wanted to see the Item Administrator functionality in action, 
I've added a sample Item Administrator to the DSpace Demo Site 
(http://demo.dspace.org).  On this site, if you login as the Demo 
Submitter (dspacedemo+sub...@gmail.com), you'll have Administrative 
rights on *just* this Item: 
http://demo.dspace.org/xmlui/handle/123456789/4  (and those 
Administrative rights will allow you to edit item metadata or 
remove/change bitstreams)

Adding an Item Administrator in DSpace 1.6.0 is still a little bit of a 
manual process at this time:
(1) As an Admin, Create a new Group  add users to that group
(2) As an Admin, Edit the Item in question, and add a new Policy which 
give ADMIN rights to that Group on that item
(3) Logout  Login as a Group member. Access that Item as a member of 
that new group -- you should have full Admin rights on that Item

So, with 1.6.0, DSpace is getting better around delegation of 
Administrative actions.  We don't yet have a setting to automatically 
give these administrative rights to all DSpace Submitters. But, I'm sure 
that is now possible with a little Java code -- and once someone builds 
that code, we can make it available to others in a future version of DSpace.

- Tim



--
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] Item upload error

2010-05-03 Thread Tim Donohue
Hi Sauleha,

Please see our How to Troubleshoot an Error page on the DSpace Wiki 
for more information on troubleshooting error messages, and where to 
find the full error messages in your DSpace log file:

http://wiki.dspace.org/confluence/display/DSPACE/Troubleshoot+an+error

Once you've found the full error message from the log file, you can 
email it to the dspace-tech mailing list and we can try and help you 
resolve the problem: 
http://sourceforge.net/mailarchive/forum.php?forum=dspace-tech

- Tim

On 4/30/2010 1:36 AM, Sauleha Durrani wrote:
 Dear all,

 I am having an internal system error' while uploading particularly
 where I have to grant the license.. Please help me out here !!

 */People may forget what you said, but they will never forget how you
 made them feel./*
 */Sauleha/*
 */ /*



 
 Hotmail: Free, trusted and rich email service. Get it now.
 https://signup.live.com/signup.aspx?id=60969



 --



 ___
 Dspace-general mailing list
 Dspace-general@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-general

--
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] DSpace 1.6.1 1.7.0 Release Schedules

2010-05-07 Thread Tim Donohue
All,

The DSpace Developers have two upcoming releases to announce to the 
DSpace Community.


DSpace 1.6.1 - Bug fix release
==

DSpace 1.6.1 is scheduled for release on Friday, May 21, 2010.

DSpace 1.6.1 is a bug-fix release which will resolve various bugs/issues 
that people have noticed in 1.6.0. This release will not introduce any 
new features, but will resolve over 20-25 bugs/issues that have been 
located since 1.6.0 was released in early March.

The 1.6.1 release is being coordinated by Kim Shepherd of the University 
of Waikato in New Zealand. A huge thanks goes out to Kim for helping to 
decrease the turnaround of this bug-fix release to the benefit of us all!

Additional information on 1.6.1 can be found on the 1.6.1 Release Notes 
page:

http://wiki.dspace.org/confluence/display/DSPACE/DSpace+Release+1.6.1+Notes


DSpace 1.7.0 - Major Release
=

In keeping with our recent decision to set a regular, timed release 
schedule, the DSpace Developers have scheduled DSpace 1.7.0 for release 
in December 2010.

(Background information about this new release planning decision can be 
found in the latest DSpace Newsletter: 
http://www.dspace.org/newsletter-newspace/NewSpace-Volume-3-Issue-20.html)

DSpace 1.7.0 will be the next major release of the software, promising 
new features and improvements to the platform.

Although the exact features have yet to be finalized, many potential 
features are listed on our new 1.7.0 Release Notes page (see below), 
along with a tentative release schedule. The 1.7.0 feature list may 
change in the coming months and only those features fully completed by 
the cut-off date of Oct 22, 2010 will be included in the 1.7.0 release.

http://wiki.dspace.org/confluence/display/DSPACE/DSpace+Release+1.7.0+Notes

As DSpace 1.7.0 is our first scheduled, time-based release, it is 
likely that it will include fewer major features than 1.6.0.  However, 
scheduling releases will benefit us all as it should decrease the delays 
in releasing new features, and increase the transparency of the 
development process. The DSpace Developers feel that these benefits will 
far outweigh the cost of having fewer major features in a given DSpace 
release.  We hope the DSpace Community will also realize the immediate 
benefits, which should allow them to receive new features more quickly, 
rather than potentially waiting years for the next major release of the 
software.

We hope that you are as excited about these announcements as we are!

As always, let us know if there are any questions.

Tim Donohue
Technical Lead for DSpace Project
DuraSpace.org

--

___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] DSpace 1.6.2 Release to fix key issues in 1.6.1

2010-06-10 Thread Tim Donohue
The DSpace Developers would like to announce the release schedule for 
DSpace 1.6.2, which resolves an few key issues in 1.6.1.

DSpace 1.6.2 is scheduled for public release on Wednesday, June 16, 2010.

DSpace 1.6.2 is a bug-fix release which will resolve two key issues 
found within 1.6.1.  This release will not introduce any new features.

Shortly after the 1.6.1 release, it came to our attention that we 
accidentally broke the Unix-based 'start-handle-server' script (which 
provides an easy way to start up the DSpace Handle Server on Unix/Linux 
servers).  Although this issue does not cause any instability with 
DSpace software itself, the developers feel that it is important enough 
that it should be resolved as soon as possible.

The DSpace 1.6.2 release resolves this 'start-handle-server' script 
issue, and also makes a few small improvements to the official DSpace 
Documentation.  In addition, 1.6.2 resolves a minor URL escaping issue 
located in the 1.6.x JSPUI.

Because of the overlooked 'start-handle-server' bug, the DSpace 
Developers have taken steps to improve our Handle Server testing 
processes for future releases. CNRI (Corporation for National Research 
Initiatives) has kindly donated a Handle System Prefix 
(http://handle.net) to the DSpace project to help us improve our future 
testing processes.  We would like to thank CNRI for their kind donation. 
  We also apologize for any issues this bug may have caused with your 
local 1.6.1 upgrades.

Sincerely,

The DSpace Developers

--
ThinkGeek and WIRED's GeekDad team up for the Ultimate 
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
lucky parental unit.  See the prize list and enter to win: 
http://p.sf.net/sfu/thinkgeek-promo
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] DSpace 1.6.2 is released, resolves issues in 1.6.1

2010-06-16 Thread Tim Donohue
All,

Today we’d like to announce the official release of DSpace 1.6.2!

DSpace 1.6.2 can be downloaded immediately at either of the following 
locations:

   * SourceForge: https://sourceforge.net/projects/dspace/files/
   * SVN: http://scm.dspace.org/svn/repo/dspace/tags/dspace-1.6.2/

DSpace 1.6.2 is a bug-fix release, which resolve several key issues in 
our 1.6.1 release. As mentioned previously 
(http://expertvoices.nsdl.org/duraspace/2010/06/11/dspace-162-release-will-fix-key-issues-in-161/),
 
shortly after the 1.6.1 release we discovered a few key issues which 
required more immediate attention. We recommend anyone running DSpace 
1.6.0 or 1.6.1 upgrade to 1.6.2 in order to resolve these issues.

DSpace 1.6.2 does not introduce any new features, it just resolves 
several issues in 1.6.1 and 1.6.0.

*Fixed issues*

Two key issues were resolved in DSpace 1.6.2.  We've fixed the broken 
'start-handle-server' script (accidentally broken in the 1.6.1 release), 
and also resolved an issue where invalid handles (identifiers) were not 
being properly escaped in the 1.6.x JSPUI.  The DSpace Developers felt 
that these two issues were important enough to warrant an immediate release.

The full details of all resolved issues are available here:
http://jira.dspace.org/jira/browse/DS/fixforversion/10040

*Acknowledgments*

The DSpace application would not exist without the hard work and support 
of the community.

Thanks to our early adopters of 1.6.1, who helped us to discover those 
few key issues we overlooked in that release.  Special thanks to the 
small team of developers (Kim Shepherd, Keith Gilbertson, Stuart Lewis, 
Tim Donohue) who pulled together fixes quickly and helped with the rapid 
turnaround between 1.6.1 and 1.6.2.  As always, thanks to Jeffrey 
Trimble in helping us quickly fix some key areas of the Documentation as 
well.

A full list of people who contributed code to DSpace 1.6.2 can be found 
at: http://scm.dspace.org/svn/repo/dspace/tags/dspace-1.6.2/dspace/CHANGES

Thanks again! Enjoy DSpace 1.6.2, and let us know what you think!

Sincerely,

The DSpace Developers

--
ThinkGeek and WIRED's GeekDad team up for the Ultimate 
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
lucky parental unit.  See the prize list and enter to win: 
http://p.sf.net/sfu/thinkgeek-promo
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] Changes in Dspace 1.6.2

2010-06-24 Thread Tim Donohue
Hi Hardik,

We actually don't maintain such a list of updated files, as it would be 
a rather long list (at least for 1.5.2 to 1.6.2).

However, if you are comfortable with command-line and have Subversion 
(svn) installed, you can generate a list of all changes using our 
Subversion repository.

You'd want to run the following command (all on one line):

svn diff http://scm.dspace.org/svn/repo/dspace/tags/dspace-1.5.2/ 
http://scm.dspace.org/svn/repo/dspace/tags/dspace-1.6.2/  1_5_to_1_6.diff

The above command will generate a full list of *all* differences between 
1.5.2 and 1.6.2 and save them into a file named '1_5_to_1_6.diff'.

WARNING -- this will likely take a long time to run, as there were a lot 
of differences between these versions.  If you wanted to just see the 
differences in the JSPUI or XMLUI, you could run a similar command, but 
only compare the 'dspace-jspui' or 'dspace-xmlui' subdirectories.

Good luck,

- Tim


On 6/24/2010 1:45 AM, Hardik Mishra wrote:
 Hello Everone,

 Currently, We are working on Dspace 1.5.2.

 We customized lots of code in both dspace-api as well as dspace-jspui.

 Is it possible to get list of files of Dspace 1.5.2 which are changed in
 Dspace 1.6.2.

 We can have files which are added but i want to details for updated file.


 Thanks   Regards
 Hardik Mishra
 Software Engineer

 Give a man a fish, and you feed him for a day. Teach a man to catch fish
 and you feed him for a lifetime.



 --
 ThinkGeek and WIRED's GeekDad team up for the Ultimate
 GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
 lucky parental unit.  See the prize list and enter to win:
 http://p.sf.net/sfu/thinkgeek-promo



 ___
 Dspace-general mailing list
 Dspace-general@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-general

--
ThinkGeek and WIRED's GeekDad team up for the Ultimate 
GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the 
lucky parental unit.  See the prize list and enter to win: 
http://p.sf.net/sfu/thinkgeek-promo
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] Announcing BibApp 1.0

2010-07-02 Thread Tim Donohue
Hi Stuart,

The reason my name is in the BibApp acknowledgments is that I was highly 
involved with BibApp when I worked at University of Illinois at 
Urbana-Champaign (my role previous to joining DuraSpace).  What has 
become BibApp 1.0 was a collaboration between colleagues/friends at 
University of Wisconsin-Madison and University of Illinois at 
Urbana-Champaign.  I am glad that I have had the opportunity to help out 
on such an exciting project!  Since I've joined DuraSpace, I've still 
been loosely involved with BibApp, but as more of an external 
consultant, and not as a programmer.  My time is more devoted to DSpace 
these days.

As to your question about DSpace-BibApp integration:  BibApp is an 
entirely separate system and open source project, which is supported by 
University of Illinois  University of Wisconsin (and I know they are 
now in search of additional collaborators). That being said, one of the 
nice features of BibApp is that it can generate SWORD-compliant 
submission packages. This means that you can gather/massage your 
metadata via BibApp, and you can also upload files (research papers, 
etc) to BibApp. BibApp will then generate a SWORD-compliant submission 
package (of those files and metadata) that you can submit to any 
SWORD-enabled repository (including DSpace, Fedora and EPrints). So, in 
that way, BibApp already has one basic integration point with your 
normal IR system.

At this time, there are no specific plans to build tighter integrations 
between DSpace and BibApp. (I'm never one to rule anything out 
completely -- but, there are no plans right now, and any plans to build 
tighter integrations would need to come from, or be approved by, our 
DSpace community.)

In my mind, BibApp is a compliment to the normal IR system, but it 
doesn't replace it by any means (especially since BibApp doesn't attempt 
to preserve/archive any files uploaded to it).  But, BibApp can be a 
tool to help make population of your IR a bit easier (which is how 
University of Wisconsin has used it early on).

There's much more information about BibApp on its website (including 
many past presentations on the 'About' page): http://bibapp.org

In addition, for those who will be at OR2010, Sarah Shreeves and Bill 
Ingram (from the BibApp team) have a presentation on BibApp 1.0 on 
Tuesday morning at 11:30am.  So, that's another opportunity to learn 
more, and ask followup questions.

- Tim

On 7/1/2010 8:52 PM, stuart yeates wrote:
 I notice you on the acknowledgement list Tim.

 Would you like to comment specifically on the extent and nature of any
 dpsace-BibApp integration?

 cheers
 stuart

 Tim Donohue wrote:
 (This message is being sent to multiple lists; please excuse
 duplication.)


 The BibApp development team is happy and proud to announce the 1.0
 release of BibApp!

 BibApp is a campus research gateway and expert finder. It matches
 researchers on your campus or research center with their publication
 data and mines that data to see collaborations, create visualizations
 of areas of research, and find experts in research areas. With BibApp,
 it is easy to see what publications can be placed on the Web for
 greater access and impact. BibApp can push those publications directly
 into an institutional repository.

 BibApp allows researchers and research groups to promote research,
 find collaborators on campus, and make research more accessible. It
 also allows libraries to better understand research happening in local
 departments, facilitate conversations about author rights with
 researchers, and ease the population of the institutional repository.
 Finally, BibApp allows campus administrators to achieve a clearer
 picture of collaboration and scholarly publishing trends on campus.

 BibApp is the result of a collaboration between the University of
 Wisconsin-Madison and the University of Illinois at Urbana-Champaign.
 The Illinois Informatics Institute at the University of Illinois
 (https://www.informatics.illinois.edu/icubed/) provided generous
 funding for the development of the 1.0 release of BibApp.

 BibApp is a Ruby on Rails application, coupled with the Solr/Lucene
 search engine, and either MySQL or PostgreSQL as its datastore. It
 uses open standards and protocols such as OpenURL and SWORD and
 automatically pulls in data from third party sources such as Google
 Books and the Sherpa/Romeo publisher policy database. BibApp imports
 publication data in RIS, MEDLINE and Refworks XML bibliography formats
 and exports data in several citation formats (APA, Chicago, IEEE, MLA,
 more) via CiteProc. BibApp also provides a web services API for
 delivering data as XML, YML, JSON, and RDF. BibApp is released under a
 University of Illinois/NCSA Open Source License
 (http://www.opensource.org/licenses/UoI-NCSA.php).

 Live installations of BibApp can be found at:

 * University of Illinois at Urbana-Champaign --
 http://connections.ideals.illinois.edu
 * The MBLWHOI Library at Woods

Re: [Dspace-general] Authority look up in 1.6.x

2010-07-19 Thread Tim Donohue
Dan,

You might find the following areas of the DSpace 1.6.2 Documentation to 
be of help:

* Intro to Authority work:
http://www.dspace.org/1_6_2Documentation/ch02.html#N105E6

* Authority Control Settings:
http://www.dspace.org/1_6_2Documentation/ch05.html#N14347

There's also much more detail on the original Wiki page (gets a bit 
technical though):
https://wiki.duraspace.org/display/DSPACE/Authority+Control+of+Metadata+Values

Hope that helps you get started.  Feel free to ask more questions on any 
of the lists if the docs are not clear.

- Tim

On 7/13/2010 3:20 PM, Daniel Sifton wrote:
 Hi,

 I’m hoping someone will share their wisdom regarding the authority
 look-up feature.

 What steps do we need to take to make this operational?

 Thanks,

 Dan

 *VIU-full-text-and-tagline_*
 *Daniel Sifton | *Coordinator, Library Automation and Technical*
 *Services | Vancouver Island University Library* | *900 Fifth St, **

 Nanaimo, BC V9R 5S5* |* Tel:* 250.753.3245, x2444 |* Email:*
 daniel.sif...@viu.ca mailto:daniel.sif...@viu.ca **|RSS
 http://feeds.feedburner.com/NewsAndEventsAtTheViuLibrary | Twitter
 http://twitter.com/VIULibrary*



 --
 This SF.net email is sponsored by Sprint
 What will you do first with EVO, the first 4G phone?
 Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first



 ___
 Dspace-general mailing list
 Dspace-general@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-general

--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] Report of DSpace RoadMap Discussions at OR10

2010-07-20 Thread Tim Donohue
All,

I wanted to send out a brief report of the DSpace RoadMap as discussed 
at Open Repositories 2010.  There are two main topics to touch on which 
may be of interest to everyone:

1. Upcoming DSpace 1.7 release
2. DSpace with Fedora Inside proposal


== DSpace 1.7 - December 2010 ==

The DSpace developers are hard at work planning out the next major 
release (1.7.0) of DSpace Software.  As announced previously, DSpace 1.7 
is scheduled for release in December 2010.  The developers met in person 
before OR10 to discuss what features should be ready for release in 1.7.

An early list of possible features can now be found on the 1.7.0 Release 
Notes page.  This list of features is still subject to change, and it's 
very likely that new features will be added to the list in the coming 
weeks/months:

https://wiki.duraspace.org/display/DSPACE/DSpace+Release+1.7.0+Notes

Also, if you are interested in reading through the meeting notes from 
our DSpace Developer meeting before OR10, those are posted publicly on 
the wiki at:

https://wiki.duraspace.org/display/DSPACE/DevMtg+2010-07-05+-+OR10+Meeting


== DSpace with Fedora Inside proposal ==

If you haven't already heard, at OR10, DuraSpace recommended that the 
DSpace and Fedora communities investigate strategies to allow DSpace 
software to run on top of the Fedora platform.  This idea is generally 
being called DSpace with Fedora Inside.

Much more detail on this recommendation can be found at:

* The proposal: 
http://expertvoices.nsdl.org/duraspace/2010/07/08/duraspace-recommends-dspace-fedora-integration-initiative/

* An FAQ around the initiative: 
https://wiki.duraspace.org/display/DSPACE/DSpace-Fedora+Integration+FAQ

* There are also some higher level details in my OR10 DSpace RoadMap 
talk: http://www.slideshare.net/tdonohue/dspace-roadmap-20102011

DuraSpace is seeking feedback on this recommendation, and is also 
looking for any interested volunteers. DuraSpace does not have the 
technical staff to do this work alone, nor would we want to. As with any 
open source development initiative, the commitment and support of the 
broader community will build a better 'end product', than if one 
institution were to implement it on their own. We are currently looking 
for volunteers to help make this initiative happen.

It's also worth noting that we do not want this initiative to hinder the 
current DSpace development process.  DSpace software will continue to 
improve and add new features as this initiative progresses.  We fully 
expect there to be several releases of DSpace software before we would 
be able to release a DSpace with Fedora Inside.

If you have thoughts on this recommendation, feel free to share them 
publicly on any DSpace listserv (or add comments to the wiki), or 
privately by emailing myself (tdono...@duraspace.org) or Valorie 
Hollister (vhollis...@duraspace.org).

Thanks!

- Tim

-- 
Tim Donohue
Technical Lead for DSpace Project
DuraSpace.org

--
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] DuraCloud is in service?

2010-07-28 Thread Tim Donohue
Hi,

First, just to clarify, DuraSpace is an organization and not a software 
product.  The open source software products that the DuraSpace 
organization helps to support are DSpace, Fedora Commons and DuraCloud.

So, I'm assuming you are probably asking about DuraCloud (since that's 
what the subject line says).

The DuraCloud software is currently in it's pilot phase and undergoing 
beta testing.  The software was recently released as Open Source.  See 
this announcement for more details:

http://expertvoices.nsdl.org/duraspace/2010/07/27/introducing-duracloud-open-source-preservation-in-the-cloud/

There is also a web seminar later on today (July 28) at 2pm EDT on 
DuraCloud, if you are interested in learning more details.  Additional 
information is available on the DuraCloud website and wiki:
http://duracloud.org/
https://wiki.duraspace.org/display/duracloud/DuraCloud


- Tim


On 7/28/2010 2:52 AM, 신진호 wrote:
 Dear Manager,

 I read through the documentations, and it sounds like DuraSpace is still
 under development? if it is then how soon should I expect to see the
 final version of DuraSpace?

 Thank you,



 --
 The Palm PDK Hot Apps Program offers developers who use the
 Plug-In Development Kit to bring their C/C++ apps to Palm for a share
 of $1 Million in cash or HP Products. Visit us here for more details:
 http://ad.doubleclick.net/clk;226879339;13503038;l?
 http://clk.atdmt.com/CRS/go/247765532/direct/01/



 ___
 Dspace-general mailing list
 Dspace-general@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-general

--
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] Authorization by IP

2010-08-17 Thread Tim Donohue
Miguel,

You're almost there.  You just need to create the group INTRANET (it 
is not auto-created for you).  After creating that group, you should be 
able to use that group to restrict IP access to whatever you need to.

- Tim

On 8/17/2010 8:44 AM, Miguel A. Robledo wrote:
 Hi,

 I'm looking for ways to create collections with read dependent of the ip
 range that is accessed.
 I saw that there is a method of authentication by IP range, but my goal
 is to give permissions to certain collections by ip and not the entire
 repository. After creating the group as

 plugin.sequence.org.dspace.authenticate.AuthenticationMethod = \
 org.dspace.authenticate.IPAuthentication, \
 org.dspace.authenticate.PasswordAuthentication

 authentication.ip.INTRANET = 10.1

 Restart tomcat and try to access my groups tab but can not find the
 group Intranet.

 This is the procedure?

 Thank you very much.

 --
 Miguel A. Robledo

 Infraestructura de Firma Digital
 Tucuman 2657 1º  Piso - Santa Fe
 Teléfono: 0342-4508700  int. 5606



 --
 This SF.net email is sponsored by

 Make an app they can't live without
 Enter the BlackBerry Developer Challenge
 http://p.sf.net/sfu/RIM-dev2dev



 ___
 Dspace-general mailing list
 Dspace-general@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-general

--
This SF.net email is sponsored by 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] A Busy Summer for DSpace -- GSoC DSpace 1.7 Updates

2010-08-24 Thread Tim Donohue
All,

The summer is always a great time to sit back, relax, and put your feet 
up.  But this summer, the DSpace developers have been hard at work 
(though, we've also taken our respective relaxation time).  We've been 
making early preparations for the upcoming DSpace 1.7 release and 
mentoring four successful student projects during the 2010 Google Summer 
of Code (GSoC).


== Google Summer of Code 2010 ==

The Google Summer of Code (http://code.google.com/soc/) is a global 
program which offers student developers stipends to write code for open 
source software projects.  This is DSpace's fourth straight year 
mentoring students to work on DSpace related projects.   This year, we 
had four great students who completed four successful projects.  More 
information on each of these projects can be found at: 
https://wiki.duraspace.org/display/DSPACE/Google+Summer+of+Code


Backport of DSpace 2.x Storage Services - Andrius Blažinskas
-
Andrius joined us for a third straight year.  The past two years, his 
projects centered around early investigation into Fedora integration. 
This year, Andrius investigated strategies to backport the DSpace 2.x 
Prototype's storage modules into our current DSpace 1.x architecture.  A 
goal of this project was to begin to investigate a potential roadmap 
towards the DSpace 2.x architecture, one which would allow you to run 
your current user interfaces on top of a more flexible storage layer. 
Although there is still more work to be done, Andrius' project helps 
bring us closer to realizing this roadmap.  In addition, Andrius' work 
over the last three years begins to showcase a potential route towards a 
DSpace with Fedora Inside 
(https://wiki.duraspace.org/display/DSPACE/DSpace-Fedora+Integration+FAQ).


DSpace REST API - Bojan Suzic
-
Bojan continued his investigation into a REST API for DSpace from last 
year's GSoC. Even if you are not a developer, you've probably heard of 
REST APIs.  Essentially, a REST API allows other systems and software to 
more easily interact with your system (and its contents) via the web. 
The DSpace Developers hope that a REST API will enable more user-based 
tools to be built around DSpace.  Bojan's summer work has provided us 
with a basic, experimental REST API.  There is still work and testing to 
do to make it fully stable, but several developers have expressed an 
interest in seeing this work move forward.  Bojan himself has also 
volunteered to help after GSoC to ensure this REST API is released in a 
future version of DSpace.


Unit Testing Project - Pere Villega
---
Pere's project sought to add a Unit Testing framework to DSpace.  A Unit 
Testing framework provides a route for improving the testing of internal 
DSpace code.  It can also help to locate bugs/issues before they are 
ever seen in the user interface.  In fact, Pere's work already helped to 
locate a minor issue or two within DSpace code which had yet to be 
noticed via a user interface.  Pere's work is also the first Google 
Summer of Code project to have ever been immediately accepted into the 
main codebase. His Unit Testing framework will be released in the 
upcoming DSpace 1.7. Keep an eye out for a formal announcement in the 
next few days!


Storage Service Implementations Based on Semantic Content Repositories - 
Yigang Zhou
---
Yigang investigated building a Semantic Storage option for DSpace.  A 
Semanic Storage option would allow DSpace to store its data in a more 
flexible/dynamic fashion, similar to Fedora's storage layer. Yigang's 
project worked alongside Andrius' project to also investigate ways to 
potentially allow DSpace 1.x to take advantage of this more flexible 
storage model.  Although there is still more work to be done, Yigang's 
project adds more context to the DSpace with Fedora Inside initiative. 
  It provides us with some immediate examples for how DSpace content 
could be stored in a more flexible fashion, which has the potential to 
inform this larger initiative.


== DSpace 1.7 Updates ==

The DSpace Developers wanted to provide a brief status update around 
DSpace 1.7.  This next major release of DSpace is still on-target to be 
released in December 2010.  Work is ongoing, and the developers are 
still working towards a final list of DSpace 1.7 new features.  An 
up-to-date list of expected 1.7 features is available on the DSpace 
1.7.0 Release Notes 
(https://wiki.duraspace.org/display/DSPACE/DSpace+Release+1.7.0+Notes) 
wiki page.  There are already two nice features which have been added to 
the codebase and finalized for the 1.7 release:

(1) Unit Testing Framework -  As mentioned above, Pere's Google Summer 
of Code work has already been approved for 1.7.0 release.  Although this 
is not a user-facing feature, it should help to ensure the DSpace 

Re: [Dspace-general] Invitation to DSpace 1.6 Usage Statistics: How Does it Work?

2010-08-30 Thread Tim Donohue
Hi Zeno,

The open-source version of this module was released as part of DSpace 
1.6.  So, it's now available in the most recent version of DSpace 
software.  Within the Documentation it is sometimes called Solr 
Statistics as Solr is the underlying software used to hold/display the 
statistics.

http://www.dspace.org/1_6_2Documentation/

Obviously, Ben Bosman will provide much more detail in his web seminar.

- Tim

On 8/29/2010 1:54 AM, tajoli wrote:
 Dear Carol

 Description: Join Ben Bosman, CTO @mire, for a free one-hour web seminar
 on
 September 8, 2010 at 11:00 EDT. He will explain how @mire’s open-source
 version of the “Content and Usage Analysis” DSpace module released
 with
 DSpace 1.6 can work for you.

 I think a web seminar about this topic is a good idea.
 But where is the open-source version of the module ?
 The releted web page, http://atmire.com/analysis.php, does not have
 a link to the code.

 Cheers
 Zeno Tajoli

 --
 Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
 Be part of this innovative community and reach millions of netbook users
 worldwide. Take advantage of special opportunities to increase revenue and
 speed time-to-market. Join now, and jumpstart your future.
 http://p.sf.net/sfu/intel-atom-d2d
 ___
 Dspace-general mailing list
 Dspace-general@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-general

--
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users 
worldwide. Take advantage of special opportunities to increase revenue and 
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] NOTICE: Ongoing DSpace Maven Issues

2010-11-09 Thread Tim Donohue
All,

First off, let me apologize in advance to anyone who has encountered 
DSpace Maven build issues yesterday or today.  These build errors 
sometimes occur when running 'mvn package' and look similar to the 
following:

[INFO] Failed to resolve artifact.

Couldn't find a version in [1.7.0.1] to match range [1.6.0.0,1.7.0.0)
   org.dspace:dspace-api-lang:jar:null

Unfortunately, our global DSpace Maven settings were accidentally messed 
up yesterday, through no real fault of our own.  Essentially, this 
occurred via a series of issues located during our attempt to release 
DSpace 1.7.0 Release Candidate 1.

During our release, we discovered our old route of getting DSpace Maven 
build packages published worldwide was unfortunately discontinued 
without our knowledge (the third party service we were using just 
stopped syncing with our servers without notifying us).

Because our old release process was ceased, over the past few days we 
quickly migrated to a different route of publishing Maven releases via 
SonaType (http://www.sonatype.com/), so that we could try to release 
DSpace 1.7.0 Release Candidate 1 in time for this week's DSpace 1.7 
Testathon.

This new route via SonaType has now unfortunately backfired on us, as 
SonaType accidentally overwrote our global Maven settings for past 
versions of DSpace software.  This means that re-building/re-installing 
of all 1.5.x and 1.6.x versions is likely affected (unless you happen to 
have a local cache of the previous Maven settings to work from).

(Please note: Although this affects re-building / re-installing of 
DSpace 1.5.x and 1.6.x versions, it will not affect the stability of 
your currently running DSpace repository.  Your existing DSpace 
repository will continue to function as normal -- you will just be 
unable to rebuild DSpace if you are doing local development work.)

We are currently working with SonaType to try to resolve these issues 
for everyone.  We apologize for the inconvenience -- it is obviously 
affecting us all.  We hope to have this resolved as soon as possible.

I'll send an update to this notice as soon as we've come to a resolution.

- Tim

-- 
Tim Donohue
Technical Lead for DSpace Project
DuraSpace.org

--
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book Blueprint to a 
Billion shares his insights and actions to help propel your 
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] NOTICE: Ongoing DSpace Maven Issues - RESOLVED

2010-11-10 Thread Tim Donohue
All,

As of this morning, all Maven build issues should be resolved.  We'd 
like to thank Juven Xu at Sonatype for helping us to resolve these 
issues in a timely fashion.

You should now be able to rebuild/reinstall DSpace as normal.  If you 
find you are still receiving localized errors/issues, it may be possible 
that your local Maven cache may need an update. Try running:

'mvn -U clean package'

The '-U' option will force your local Maven cache to update itself. 
This should allow your build to complete successfully.  After updating 
your local cache, you can run 'mvn package' as normal to rebuild DSpace.

If you notice any other issues please let us know by reporting them to 
the dspace-tech listserv (dspace-t...@lists.sourceforge.net).

Thanks for your patience,

- Tim

On 11/9/2010 11:56 AM, Tim Donohue wrote:
 All,

 First off, let me apologize in advance to anyone who has encountered
 DSpace Maven build issues yesterday or today. These build errors
 sometimes occur when running 'mvn package' and look similar to the
 following:

 [INFO] Failed to resolve artifact.

 Couldn't find a version in [1.7.0.1] to match range [1.6.0.0,1.7.0.0)
 org.dspace:dspace-api-lang:jar:null

 Unfortunately, our global DSpace Maven settings were accidentally messed
 up yesterday, through no real fault of our own. Essentially, this
 occurred via a series of issues located during our attempt to release
 DSpace 1.7.0 Release Candidate 1.

 During our release, we discovered our old route of getting DSpace Maven
 build packages published worldwide was unfortunately discontinued
 without our knowledge (the third party service we were using just
 stopped syncing with our servers without notifying us).

 Because our old release process was ceased, over the past few days we
 quickly migrated to a different route of publishing Maven releases via
 SonaType (http://www.sonatype.com/), so that we could try to release
 DSpace 1.7.0 Release Candidate 1 in time for this week's DSpace 1.7
 Testathon.

 This new route via SonaType has now unfortunately backfired on us, as
 SonaType accidentally overwrote our global Maven settings for past
 versions of DSpace software. This means that re-building/re-installing
 of all 1.5.x and 1.6.x versions is likely affected (unless you happen to
 have a local cache of the previous Maven settings to work from).

 (Please note: Although this affects re-building / re-installing of
 DSpace 1.5.x and 1.6.x versions, it will not affect the stability of
 your currently running DSpace repository. Your existing DSpace
 repository will continue to function as normal -- you will just be
 unable to rebuild DSpace if you are doing local development work.)

 We are currently working with SonaType to try to resolve these issues
 for everyone. We apologize for the inconvenience -- it is obviously
 affecting us all. We hope to have this resolved as soon as possible.

 I'll send an update to this notice as soon as we've come to a resolution.

 - Tim


--
The Next 800 Companies to Lead America's Growth: New Video Whitepaper
David G. Thomson, author of the best-selling book Blueprint to a 
Billion shares his insights and actions to help propel your 
business during the next growth cycle. Listen Now!
http://p.sf.net/sfu/SAP-dev2dev
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] Issues Regarding Labelling

2011-01-03 Thread Tim Donohue
Hi Sal,

There's a How To guide on the DSpace Wiki which should help you 
resolve this issue:

https://wiki.duraspace.org/pages/viewpage.action?pageId=19006259

We have many how-to guides/resources on the Wiki which can be used to 
resolve these sorts of common issues:

* How To Guides: https://wiki.duraspace.org/display/DSPACE/How+To+Guides
* DSpace Resources: 
https://wiki.duraspace.org/display/DSPACE/DSpaceResources

Good luck,

- Tim

On 12/30/2010 11:00 PM, Sauleha Durrani wrote:
 Dear Sirs / Madams,


 We have installed Dspace at our university library, for keeping records.
 We are facing a few issues in customization of the software. When
 results are shown on browsing by Title page, some of the fields are
 now showing labels. For example :
 ???itemlist.dc.contributor.advisor??? Here the Label should be Advisor
  . We know that the changes are to be made in the massages property
 file. Can anyone guide us that where the 'jsp' page for this
 customization is located. I am also attaching a snap shot of the page.


 Thank you very much. Waiting in anticipation for the reply.
   Sal Durrani



 --
 Learn how Oracle Real Application Clusters (RAC) One Node allows customers
 to consolidate database storage, standardize their database environment, and,
 should the need arise, upgrade to a full multi-node Oracle RAC database
 without downtime or disruption
 http://p.sf.net/sfu/oracle-sfdevnl



 ___
 Dspace-general mailing list
 Dspace-general@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-general

--
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and, 
should the need arise, upgrade to a full multi-node Oracle RAC database 
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] Turn off submission email feature?

2011-01-26 Thread Tim Donohue
Hi Stuart,

This remains unchanged in 1.6 and 1.7.  It looks like we've never 
received a patch to make this configuration, and it's never been entered 
into our Issue Tracker system as a desirable feature:

https://jira.duraspace.org/browse/DS

If you or anyone else has time to devote to either developing such a 
feature or even just describing some of the possible use cases / 
potential solutions, I'd encourage you to enter a new issue/feature 
request in our tracker system.

This will ensure that the DSpace developers are aware of your request, 
and help us to track it and (hopefully) add it to a future version of 
DSpace. Please note that, as we are all volunteers, we cannot guarantee 
a particular feature will make it into the next release. However, if we 
can find a volunteer developer, or if someone from the community 
volunteers to provide a patch, it can help to expedite that process.

Much more information on contributing to DSpace (via either 
ideas/feature requests or code) is available on this Wiki page:
https://wiki.duraspace.org/display/DSPACE/HowToContribute

Let us know if you have any further questions.

- Tim

On 1/24/2011 6:11 PM, stuart yeates wrote:
 Is this still the case in 1.6, or is there now an easier way to turn off
 emails?

 Looking through the source I'm not seeing anything like this patch...

 cheers
 stuart

 On 04/03/09 20:59, Claudia Jürgen wrote:
Hi Kelvin,
   
there is no configuration option to disable the email notification for
archived submissions.
   
You may change it in
dspace-api/src/main/java/org/dspace/workflow/WorkflowManager.java
just comment this line out:
notifyOfArchive(c, myitem, mycollection);
Then ran mvn package, ant update and redploy
   
Or you can make it configurable, see attached patch. The patch
 (against
1.5.x) defaults to notify for backward compability. Change the
configuration parameter to false if you want to disable notification.
   
Hope that helps
   
Claudia Jürgen
   
   
Kelvin Yang schrieb:
Hi all,
   
I was wondering if there is any way to turn off the individual
submission email you get each time you do a submission.
   
I was looking in dspace.cfg but no luck finding it.
It just gets too repetitive receiving email for every submission
 someone
does.
   
Thanks.
___
Dspace-general mailing list
dspace-gene...@mit.edu
http://mailman.mit.edu/mailman/listinfo/dspace-general



 --
 Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
 Finally, a world-class log management solution at an even better price-free!
 Download using promo code Free_Logger_4_Dev2Dev. Offer expires
 February 28th, so secure your free ArcSight Logger TODAY!
 http://p.sf.net/sfu/arcsight-sfd2d



 ___
 Dspace-general mailing list
 Dspace-general@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-general

--
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires 
February 28th, so secure your free ArcSight Logger TODAY! 
http://p.sf.net/sfu/arcsight-sfd2d
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] JSpui and Xmului directory are not found after install in Dspace 1.7

2011-02-03 Thread Tim Donohue
Hi Indu,

It looks like you may be building DSpace 1.7 using an unsupported 
version of Maven.

There are known issues with building DSpace 1.7 using Maven 2.0.x or 
2.1.x.  They are described in more detail here:
https://jira.duraspace.org/browse/DS-788

The fix is to upgrade to Maven 2.2.x or above, and rebuild DSpace 1.7. 
After upgrading Maven, you should see the XMLUI and JSPUI directories 
get built properly. See the online Installation docs for more info:
https://wiki.duraspace.org/display/DSDOC/Installation#Installation-ApacheMaven2.2.xorlater%28Javabuildtool%29

Good luck,

- Tim

On 2/3/2011 7:19 AM, इन्‍दु भूषण Indu Bhushan wrote:
 Dear Sir,

 I could not solved login/password  and pdf thumbnail  problem in 1.6.2
 so i want to switch directly to 1.7. I am getting following error after
 fresh install and it is not creating JSpui and Xmlui directory. the list
 of directory created after ant fresh install is also attached herewith

 Please give me suggestion and help me.

 With regards
 Indu Bhushan
 RRCAT Indore


 [dspace@library-1 dspace-1.7.0-build.dir]$ ant fresh_install

 update_geolite:
   [echo] Downloading:
 http://geolite.maxmind.com/download/geoip/database/GeoLiteCity.dat.gz
[get] Getting:
 http://geolite.maxmind.com/download/geoip/database/GeoLiteCity.dat.gz
[get] To: /diglib/dspace/config/GeoLiteCity.dat.gz
[get] Error getting
 http://geolite.maxmind.com/download/geoip/database/GeoLiteCity.dat.gz to
 /diglib/dspace/config/GeoLiteCity.dat.gz

 BUILD FAILED
 /diglib/dspace1.7/dspace/target/dspace-1.7.0-build.dir/build.xml:882:
 The following error occurred while executing this line:
 /diglib/dspace1.7/dspace/target/dspace-1.7.0-build.dir/build.xml:945:
 The following error occurred while executing this line:
 /diglib/dspace1.7/dspace/target/dspace-1.7.0-build.dir/build.xml:931:
 java.net.SocketException: Network is unreachable
  at java.net.PlainSocketImpl.socketConnect(Native Method)
  at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
  at
 java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
  at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
  at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
  at java.net.Socket.connect(Socket.java:529)
  at java.net.Socket.connect(Socket.java:478)
  at sun.net.NetworkClient.doConnect(NetworkClient.java:163)
  at sun.net.www.http.HttpClient.openServer(HttpClient.java:394)
  at sun.net.www.http.HttpClient.openServer(HttpClient.java:529)
  at sun.net.www.http.HttpClient.init(HttpClient.java:233)
  at sun.net.www.http.HttpClient.New(HttpClient.java:306)
  at sun.net.www.http.HttpClient.New(HttpClient.java:323)
  at
 sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLConnection.java:860)
  at
 sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:801)
  at
 sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection.java:726)
  at
 org.apache.tools.ant.taskdefs.Get$GetThread.openConnection(Get.java:662)
  at org.apache.tools.ant.taskdefs.Get$GetThread.get(Get.java:581)
  at org.apache.tools.ant.taskdefs.Get$GetThread.run(Get.java:571)
 *LIST OF DIRECTORY (JSpui and Xmului not found)*
 =
 [dspace@library-1 dspace-1.7.0-build.dir]$ cd /diglib/dspace
 [dspace@library-1 dspace]$ ls
 assetstore  bin  config  etc  exports  handle-server  lib  log  reports
   search  solr  upload  webapps

 [dspace@library-1 dspace]$ cd webapps/
 [dspace@library-1 webapps]$ ls
 admincomponents  exception2html.xslt  image
   print.css statistics tools
 aspects  controlledvocabularyfavicon.ico
   index.jsp  register  styles.css utils.js
 browse   display-item.jspfeedback layout
  robots.txtsubmit WEB-INF
 collection-home.jsp  display-statistics.jsp  help login
   searchsuggestworkspace
 community-home.jsp   dspace-adminhome.jsp
 META-INF   sitemap.xmap  themes
 community-list.jsp   error   i18n
 mydspace   statictombstone.jsp
 ===




 --
 Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
 Finally, a world-class log management solution at an even better price-free!
 Download using promo code Free_Logger_4_Dev2Dev. Offer expires
 February 28th, so secure your free ArcSight Logger TODAY!
 http://p.sf.net/sfu/arcsight-sfd2d



 ___
 Dspace-general mailing list
 Dspace-general@lists.sourceforge.net
 

[Dspace-general] DSpace 1.7.1 tentatively scheduled for end of March

2011-02-23 Thread Tim Donohue
All,

Today, in our weekly meeting, the DSpace developers decided to 
tentatively schedule the DSpace 1.7.1 (bug-fix only) release for March 
25, 2011. Peter Dietz of Ohio State University Libraries will coordinate 
this minor release.

As you are aware, DSpace 1.7.0 was released on December 17, 2010. Since 
that time, DSpace 1.7.0 has proven to be very stable overall. However, 
we have discovered a few issues that we feel would be worth resolving 
before 1.8.0 is released in October 2011.

The primary issues we will be working to fix for 1.7.1 revolve around 
bugs with SWORD-based submissions and Oracle compatibility issues. 
Other minor fixes will also be included in 1.7.1.

For more information about the 1.7.1 Release, and a listing of issues 
that have been fixed or will be fixed, please visit:

https://wiki.duraspace.org/display/DSPACE/DSpace+Release+1.7.1+Notes

If you'd like to help out, also visit the above page for more 
information on how you can help with this bug-fix release.

Thanks!

The DSpace Committers Group

--
Free Software Download: Index, Search  Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] OR11 -- Deadline for proposals extended to March 7

2011-02-24 Thread Tim Donohue
The Sixth International Conference on Open Repositories (OR11) will be 
held June 7 - 11 in Austin, Texas. In light of the growing maturity of 
the repository arena, the primary theme of this year's conference is 
Collaboration and Community: The Social Mechanics of Repository 
Systems. Jim Jaglieski, a founder of the Apache Software Foundation, 
will provide the keynote, addressing what ASF has learned on both fronts 
over more than a decade of support for open source software projects.

The conference steering committee welcomes 2-4 page proposals for 
presentations or panels on this topic, or dealing with any of the other 
conference themes by *March 7, 2011*.

In addition to papers and panels, the committee also welcomes proposals for

   * 24x7 Presentations -- 24 slides in no more than 7 minutes
   * Posters
   * User Group presentations for DSpace, Eprints and Fedora
   * Workshops, Birds of Feather and Tutorials

Key dates:

   * All proposals are due by March 7 (extended by one week from the 
original 2/28 date)
   * Notification date for papers  panels: April 4, 2011
   * Notification date for 24x7's, Posters, Workshops: April 14, 2011
   * Conference dates: June 7 - 11

Be an integral part of this year's event by sharing local developments 
and advances through any of these channels. More information can be 
found at these key links:

   * Call for Papers: 
https://conferences.tdl.org/OR2011/OR2011main/schedConf/cfp
   * Track Policies: 
https://conferences.tdl.org/OR2011/OR2011main/schedConf/trackPolicies
   * OR11 Sponsorship Information: 
https://conferences.tdl.org/OR2011/OR2011main/about/editorialPolicies#custom0


--
Free Software Download: Index, Search  Analyze Logs and other IT data in 
Real-Time with Splunk. Collect, index and harness all the fast moving IT data 
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business 
insights. http://p.sf.net/sfu/splunk-dev2dev 
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] Call for Mentors Project Ideas for DuraSpace Google Summer of Code

2011-03-21 Thread Tim Donohue
Dear DuraSpace Community,

DuraSpace has been accepted as a participant in this year's Google 
Summer of Code (GSoC) student internship program 
(http://socghop.appspot.com/)!

Our community has participated in GSoC for the last four years 
(2007-2010), completing a total of 16 successful student projects over 
the years. During the last four years, only DSpace software has taken 
part. This year, we hope to have GSoC projects for all three DuraSpace 
technologies: DSpace, Fedora and DuraCloud!

== Call for DuraSpace Project Ideas  Mentors ==

The purpose of DuraSpace's participation in GSoC is to:
(1) promote involvement of new students as open source developers within 
the DuraSpace Community,
(2) provide opportunities for existing community members to lead within 
the community as mentors, and
(3) make some exciting improvements to DuraSpace technologies along the way.

We would like to encourage all community members, potential mentors and 
students to post their ideas for GSoC 2011 projects on our wiki. We have 
separate Project Ideas pages listed for each DuraSpace technology:

* DSpace Ideas: 
https://wiki.duraspace.org/display/GSOC/DSpace+Summer+of+Code
* Fedora Ideas: 
https://wiki.duraspace.org/display/GSOC/Fedora+Summer+of+Code+Ideas
* DuraCloud Ideas: 
https://wiki.duraspace.org/display/GSOC/DuraCloud+Summer+of+Code+Ideas

Project ideas which span multiple technologies (e.g. DSpace  Fedora, or 
Fedora  DuraCloud) may be listed on either Ideas Page above or 
cross-listed.

We need to get as many ideas posted by MONDAY, MARCH 28TH, as this is 
when the application period begins for students (student applications 
are accepted until Fri, April 8, 19:00 UTC).

If you would like to be a mentor (or co-mentor) on the project(s) you 
proposed, please add your name to the 'Mentor Volunteer(s)' column next 
to the project information.

To be a GSoC Mentor, you should be an active developer in the community 
and keenly interested in leading a student through a software 
development project. It is not required that you be a Committer, but it 
is recommended that you try to find a Committer who is willing to 
sponsor or co-mentor the project. As necessary, we can help you to 
find a Committer to work with.

The final list of mentors will be selected based on whether we have 
students interested in your project. If we end up with more mentors than 
students, you are also welcome to join up and co-mentor a different 
student project.

For more information about DuraSpace GSoC, please see our DuraSpace 
Summer of Code page: https://wiki.duraspace.org/display/GSOC/

INTERESTED STUDENTS: Don't worry, we haven't forgotten you! You are also 
welcome to suggest projects and take part in this early discussion 
period. As we get closer to the student application period, we'll send 
out more information about our GSoC application process this year. Until 
then, feel free to check out early GSoC details at: 
https://wiki.duraspace.org/display/GSOC/

Get excited and join in the fun!

--
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] Calling all Students, GSoC 2011 Applications due by April 8

2011-03-29 Thread Tim Donohue
Calling all students, Google Summer of Code 2011 Applications are due by 
April 8!

(Professors, please share this with your students! Librarians, please 
forward to both professors and students!)

YOU CAN EARN $5,000 FOR A BIT OF SUMMER CODING!?!

That's right! Apply for Google Summer of Code and you can earn $5000 USD 
for a summer's worth of work!  In addition, you will gain valuable 
experience in a friendly open source community (looks great on your 
resume!). You may even see your code as part of one of our DuraSpace 
technologies!

DuraSpace is specifically looking for GSoC students who are interested 
in one or more of the following topics: digital preservation/curation, 
institutional repositories, digital libraries/archives, cloud computing, 
semantic web, web services/applications, open access publishing, and 
generally helping to ensure digital content can be accessible over the 
long term.

For GSoC 2011, we are looking for students interested in working on any 
of our three open source technology platforms:
* DSpace - a turnkey institutional repository application
* Fedora - a framework for building digital repositories
* DuraCloud - a hosted service for managing digital content in the cloud

For a list of all current DuraSpace GSoC Project Ideas, please visit:
https://wiki.duraspace.org/display/GSOC/

Students are also welcome to suggest their own Project Ideas! If you'd 
like to begin the discussion early, please join our 'duraspace-gsoc' 
mailing list:
http://groups.google.com/group/duraspace-gsoc/

If you aren't yet convinced, here are some videos/propaganda to 
encourage your participation in GSoC:
* GSoC 2011 Flyers: 
http://code.google.com/p/google-summer-of-code/wiki/GsocFlyers
* From GSoC 2009 - GSoC experiences and a History of Open Source: 
http://www.youtube.com/watch?v=vBRRR0BQyz0
* From GSoC 2008 - Google Wants to Give you Money!: 
http://idyll.dreamhosters.com/transfer/gsoc-2008-screencast.mp4

To participate in GSoC 2011 as a student, please visit the Google Summer 
of Code homepage to submit your application:
http://www.google-melange.com/

In addition, we ask that you send in your application using the 
DuraSpace application template available on our GSoC profile:
http://www.google-melange.com/gsoc/org/google/gsoc2011/duraspace

More information about DuraSpace and our projects can be found on our 
GSoC 2011 wiki page:
https://wiki.duraspace.org/display/GSOC/

The student application period began on Monday, March 28th and ends on 
Friday, April 8. See the GSoC 2011 Site (http://www.google-melange.com/) 
for more details.

--
Enable your software for Intel(R) Active Management Technology to meet the
growing manageability and security demands of your customers. Businesses
are taking advantage of Intel(R) vPro (TM) technology - will your software 
be a part of the solution? Download the Intel(R) Manageability Checker 
today! http://p.sf.net/sfu/intel-dev2devmar
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] Unable to get success in mvn package

2011-03-30 Thread Tim Donohue
Hi Imran,

It looks like you are running 'mvn package' from the wrong directory.

You should be running 'mvn package' from the [dspace-source]/dspace/ 
directory, which based on your jpeg file should be:

C:\dspace-1.7.1-release\dspace\

This is detailed in the Installation Instructions at:
https://wiki.duraspace.org/display/DSDOC/Installation#Installation-Installation 
(see step #7)

So, if you run:

'cd C:\dspace-1.7.1-release\dspace\'

and, then run:

'mvn package'

then, that should hopefully resolve the errors you are seeing.

Good luck,

- Tim


On 3/30/2011 1:09 PM, Imran Mansuri wrote:
   Dear

I have installed dspace prerequisite successfully along with path
 variables also on Windows7 and Xp  32bit version many times on various
 system  and i installed all latest version of prerequisites
 But moment i try to download mvn package  under  BELOW DIRECTORY

 C:\dspace-1.7.1-release  mvn package

   I am unable to  get success in  mvn package and  I found same message
 again and again
   message which i got  attached in jpeg file

Earlier i had installed Dspace  many times in various systems on
 various version of Winxp and Vista moreover  i used it but suddenly this
 problems being faced by me


Kindly guide me


 With Regards
 Imran Mansuri
 INFLIBNET Centre



 --
 Create and publish websites with WebMatrix
 Use the most popular FREE web apps or write code yourself;
 WebMatrix provides all the features you need to develop and
 publish your website. http://p.sf.net/sfu/ms-webmatrix-sf



 ___
 Dspace-general mailing list
 Dspace-general@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-general

--
Create and publish websites with WebMatrix
Use the most popular FREE web apps or write code yourself; 
WebMatrix provides all the features you need to develop and 
publish your website. http://p.sf.net/sfu/ms-webmatrix-sf
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] Storage capacity of Dspace to version 1.7.1 - Help

2011-06-17 Thread Tim Donohue
Hi Patrícia,

DSpace itself uses the filesystem for storage. So you are only limited 
by your available file system space. So, if your 3 million items take up 
3TB of space, then you will need to ensure DSpace has access to 3TB 
worth of local (or mounted) storage space.

In the past (DSpace 1.6 and previous) there were some performance issues 
with DSpace when you stored millions of items. However, we've made some 
significant performance/scalability improvements to DSpace 1.7.x.  So, 
at this point in time, we believe you will achieve good performance when 
storing millions of items (admittedly, most large DSpace installs just 
store hundreds of thousands of items, so we haven't done much testing 
with millions of items).

That being said, to achieve optimal performance, you likely will need to 
ensure your server has appropriate memory and processing power.

We have some hints on ways to performance tune your DSpace installation 
on our wiki at:

* https://wiki.duraspace.org/display/DSPACE/SystemAdministrators
* https://wiki.duraspace.org/display/DSPACE/HowToPerformanceTuneForDspace

If you run into any issues, please feel free to email our DSpace 
Technology list: https://lists.sourceforge.net/lists/listinfo/dspace-tech/

Good luck,

- Tim


On 6/16/2011 5:00 PM, Patricia Coelho Ferreira Meneses da Silva wrote:
 Hi!
 Anyone know what the storage capacity of Dspace to version 1.7.1? Does
 anyone know the capacity of items that can be included in each collection?

 We want to store more than 3 million items and do not know if the system
 supports.
 Thanks.
 Patrícia Coelho



 --
 EditLive Enterprise is the world's most technically advanced content
 authoring tool. Experience the power of Track Changes, Inline Image
 Editing and ensure content is compliant with Accessibility Checking.
 http://p.sf.net/sfu/ephox-dev2dev



 ___
 Dspace-general mailing list
 Dspace-general@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-general

--
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] Something goes wrong on install (newbie question :( )

2011-07-18 Thread Tim Donohue
Hi Daniel,

What version of Maven  Java are you using?

Please double check you have all the necessary prerequisites.  You must 
have Maven 2.2.x, and you must be using Oracle/Sun JDK 6 or later.

https://wiki.duraspace.org/display/DSDOC/Installation#Installation-PrerequisiteSoftware

It looks like the Ant Installer is not able to find its necessary 
install files. Which could mean one of the following:
* You may be using the wrong version of Maven (which may have built the 
installer improperly)
* You may not be using the Oracle/Sun version of Java
* Or, it's possible there's a permissions problem and the installer 
wasn't able to copy its files to the proper location

If you are still having more issues, please feel free to respond back to 
this list, and we can try and help!  Again, the above resolutions are 
really just a guess, based on the limited information. But, if you 
follow up with more info, we may be able to better figure out what may 
be going on.

- Tim

On 7/18/2011 4:51 AM, Daniel Bourrion wrote:
 Hi
 I'm trying to install dspace in order to test it (we think of using it
 for an academic OAI repository)

 Got that (sad) message (that I don't understand) during ant fresh_install :

 ---
 setup_database:
   [java] 2011-07-18 11:40:18,481 INFO
 org.dspace.core.ConfigurationManager @ Loading system provided config
 property (-Ddspace.configuration): config/dspace.cfg
   [java] 2011-07-18 11:40:18,486 INFO
 org.dspace.core.ConfigurationManager @ Using default log4j provided log
 configuration,if unintended, check your dspace.cfg for (log.init.config)
   [java] 2011-07-18 11:40:18,486 INFO
 org.dspace.storage.rdbms.InitializeDatabase @ Initializing Database
   [java] 2011-07-18 11:40:18,487 FATAL
 org.dspace.storage.rdbms.InitializeDatabase @ Caught exception:
   [java] java.io.FileNotFoundException: database_schema.sql (No such
 file or directory)
   [java] at java.io.FileInputStream.open(Native Method)
   [java] at java.io.FileInputStream.init(FileInputStream.java:137)
   [java] at java.io.FileInputStream.init(FileInputStream.java:96)
   [java] at java.io.FileReader.init(FileReader.java:58)
   [java] at
 org.dspace.storage.rdbms.InitializeDatabase.getScript(InitializeDatabase.java:119)
   [java] at
 org.dspace.storage.rdbms.InitializeDatabase.main(InitializeDatabase.java:68)

 BUILD FAILED
 /home/dspace/Bureau/dspace-1.7.2-release/dspace/target/dspace-1.7.2-build.dir/build.xml:765:
 Java returned: 1

 -


 Should somebdy help me ?
 Thanks a lot
 Best
 D.



 --
 AppSumo Presents a FREE Video for the SourceForge Community by Eric
 Ries, the creator of the Lean Startup Methodology on Lean Startup
 Secrets Revealed. This video shows you how to validate your ideas,
 optimize your ideas and identify your business strategy.
 http://p.sf.net/sfu/appsumosfdev2dev



 ___
 Dspace-general mailing list
 Dspace-general@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-general

--
AppSumo Presents a FREE Video for the SourceForge Community by Eric 
Ries, the creator of the Lean Startup Methodology on Lean Startup 
Secrets Revealed. This video shows you how to validate your ideas, 
optimize your ideas and identify your business strategy.
http://p.sf.net/sfu/appsumosfdev2dev
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] Command-line import vs review policies

2011-08-10 Thread Tim Donohue
Vika,

By default, the Item Importer skips any Collection Workflows.  However, 
you can tell it to obey workflows by passing it the -w flag.

For more info, see the Documentation at:

https://wiki.duraspace.org/display/DSDOC/System+Administration#SystemAdministration-ImportingItems

- Tim

On 8/10/2011 4:15 PM, Zafrin, Vika wrote:
 I just did a test run of a command-line import into a collection that has 
 Workflow Step 2 set (Accept/Reject/Edit Metadata).  I was able to import 
 without having to go through this step -- which is great!  That's what I 
 want!  But did this happen because in the line command I used an eperson 
 that's in the Administrator group?  Or does command-line import always bypass 
 the review workflow steps?

 Thanks!
 -Vika

 Vika Zafrin
 Institutional Repository Librarian
 Boston University
 +1.617.358.6370


 --
 uberSVN's rich system and user administration capabilities and model
 configuration take the hassle out of deploying and managing Subversion and
 the tools developers use with it. Learn more about uberSVN and get a free
 download at:  http://p.sf.net/sfu/wandisco-dev2dev
 ___
 Dspace-general mailing list
 Dspace-general@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-general

--
uberSVN's rich system and user administration capabilities and model 
configuration take the hassle out of deploying and managing Subversion and 
the tools developers use with it. Learn more about uberSVN and get a free 
download at:  http://p.sf.net/sfu/wandisco-dev2dev
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] Announcing the DSpace 1.8.0 Testathon : Sept 12-23

2011-09-07 Thread Tim Donohue
DSpace Community,

On behalf of the DSpace Committers, we'd like to formally announce the 
DSpace 1.8.0 Testathon will begin on Monday, September 12 and last until 
Friday, September 23.

This is your opportunity to get a preview of the upcoming 1.8.0 release, 
while also helping us to fully test the system and squash any last bugs!

During the Testathon (September 12-23), you can help us by testing an 
early version of 1.8.0 on our Demo Site (http://demo.dspace.org) or 
other available Testathon sites (TBA).

If you are technically inclined, next week you may also download a copy 
of this early release (1.8.0 RC1) and install it on your own local 
development server: 
https://sourceforge.net/projects/dspace/files/DSpace%20Release%20Candidate/

Some key 1.8.0 features to be on the lookout for include:
* Configurable Reviewer Workflow - adds ability to configure your own 
local approval workflow processes
* Media RSS Feeds - Allows DSpace media content to now be published to 
iTunes U, iTunes podcasts, etc.
* A SWORD Client - allows DSpace to send its content (via SWORD) to 
another SWORD enabled repository (including another DSpace)
* Reordering of Bitstreams - Allows you to reorganize the files attached 
to an item into a defined order.
* Virus checking during Submission process - when enabled, allows you to 
virus check all files *before* they get into DSpace.
* Compatibility with SWORD v2 protocol - allows SWORD 2 clients to 
submit packages to DSpace.
* Rewrite of Creative Commons Licensing - improves the process for 
adding a CC License to content during the submission process.
* Split up the 'dspace.cfg' file into smaller, more easily managed 
configuration files.
* Numerous other features, improvements  bug fixes

A full list of features/changes in DSpace 1.8.0 can be found at: 
https://wiki.duraspace.org/display/DSPACE/DSpace+Release+1.8.0+Notes

For additional information on the Testathon, how you can help, and how 
you can provide feedback, please visit: 
https://wiki.duraspace.org/display/DSPACE/DSpace+Release+1.8.0+Testathon+Page 


Thanks! We hope you enjoy your preview of 1.8.0 next week! Don't 
hesitate to get in touch with any feedback!


--
Using storage to extend the benefits of virtualization and iSCSI
Virtualization increases hardware utilization and delivers a new level of
agility. Learn what those decisions are and how to modernize your storage 
and backup environments for virtualization.
http://www.accelacomm.com/jaw/sfnl/114/51434361/
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] Welcome to the latest DSpace committer: Kevin Van de Velde

2011-09-13 Thread Tim Donohue
Dear DSpace Community,

The DSpace committers team are delighted to announce a new member to the 
group: Kevin Van de Velde from @mire. Please join us in welcoming him!

Kevin has worked tirelessly for several years as a DSpace developer for 
@mire. A significant number of new features for DSpace have involved his 
participation. Kevin has been active in helping to improve the DSpace 
backend (especially DSpace Service Manager), along with contributing to 
the DSpace Solr Statistics and Discovery projects. For the upcoming 
1.8.0 release, Kevin added the ability for Administrators to reorder 
bitstreams (files) within a DSpace Item. In addition, he helped to 
create the new 1.8.0 Configurable Workflow feature. (More information on 
those new features is available in our 1.8.0 Release Notes: 
https://wiki.duraspace.org/display/DSPACE/DSpace+Release+1.8.0+Notes)

Kevin comments on his interest in being a committer:  I want to be a 
committer because, even though I work for @mire, I want to contribute 
even more than my internal activities within @mire allow. As an example 
of my recent independent work outside of @mire, I created a new backend 
and a new Spring based configuration for Discovery Indexing, Filter and 
Facet Configurations. I also recently worked to extend the DSpace 
Service managers configuration capabilities. Since I work with DSpace 
day in and day out, I hope to provide many bug fixes to issues back 
to the community codebase on a regular basis.

We are always on the lookout for new developers, contributors, and 
committers within the DSpace community. Anyone who would like to get 
more involved is encouraged to do so. You are also welcome to contact us 
at any time if you'd like some ideas of how to start contributing:

- https://wiki.duraspace.org/display/DSPACE/DSpaceContributors

Contributions can take many forms, from writing code to editing 
documentation, or testing new releases to designing new themes for our 
user interfaces.

If you or someone you know has been an active DSpace contributor for 
some time, you can also nominate that person to become our next 
committer! Nomination details are available at:

- https://wiki.duraspace.org/display/DSPACE/Committer+Nominations

Thanks,

The DSpace Committers Group


--
BlackBerryreg; DevCon Americas, Oct. 18-20, San Francisco, CA
Learn about the latest advances in developing for the 
BlackBerryreg; mobile platform with sessions, labs  more.
See new tools and technologies. Register for BlackBerryreg; DevCon today!
http://p.sf.net/sfu/rim-devcon-copy1 
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] Statistics for Individual Author/Creators

2011-09-14 Thread Tim Donohue
Just a note:  It'd be great to see this sort of work come back into 
DSpace if you feel it could be generalized, Andrea!  Nice work!

- Tim

On 9/13/2011 6:31 PM, Andrea Schweer wrote:
 Hi Alvin,

 On 13/09/11 04:42, Hutchinson, Alvin wrote:
 Has anyone tried to generate custom statistics for individual
 author/creators?

 I wrote customised statistics for the four repositories that I'm looking
 after. Three of these are publicly available:

 http://otago.ourarchive.ac.nz/stats
 http://researchcommons.waikato.ac.nz/stats
 http://unitec.researchbank.ac.nz/stats

 These links go to the statistics pages for the entire repository, which
 include top author statistics; statistics pages for each author are also
 available (and linked from the main statistics page).

 My customisations build on the solr-based statistics that were
 introduced with DSpace 1.6. I customised these quite heavily; the most
 important addition for author statistics is that the authors of an item
 are included in the data posted to solr for item page views and file
 downloads. That way, I can then query solr for all item page views /
 file downloads for a given author in the same way as it's possible in
 the default solr stats to query for all item page views / file downloads
 in a given collection etc.

 There are drawbacks to including author data directly in the statistics
 data. The alternative is something similar to what Peter Dietz described
 in his response over on dspace-tech: get all of an author's item ids
 (maybe from discovery, if you want to stick to solr) and then query by
 those.

 I'm happy to share more technical details of my customisations if you or
 anyone else is interested.

 cheers,
 Andrea


--
BlackBerryreg; DevCon Americas, Oct. 18-20, San Francisco, CA
Learn about the latest advances in developing for the 
BlackBerryreg; mobile platform with sessions, labs  more.
See new tools and technologies. Register for BlackBerryreg; DevCon today!
http://p.sf.net/sfu/rim-devcon-copy1 
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] Ant Fresh_install error

2011-09-20 Thread Tim Donohue
Hi Leeladharan,

It looks like there may be a few issues here.

(1) It looks like you are running 'ant fresh_install' against a database 
that already exists. The error message says that it is attempting to 
create values in your database which already exist. You will need to 
clear out your existing Database entirely (or delete  recreate it). The 
'ant fresh_install' command needs to be run on an empty database.

(2) You also mentioned that you are running Maven 3.0.3.  DSpace 1.7.x 
is only compatible with Maven 2.2.x. So, you may run into other build 
issues when running Maven 3 with DSpace 1.7.x. For more information see 
the 1.7.x prerequisites at: 
https://wiki.duraspace.org/display/DSDOC/Installation#Installation-ApacheMaven2.2.x%28Javabuildtool%29

Good luck,

- Tim

On 9/20/2011 2:38 AM, leeladharan manavalan wrote:
 Hi all,
  I am trying to install DSpace on Windows. I am using the following
 softwares


 Apache ant 1.8.2

 Apache maven 3.0.3

 Apache Tomcat 7.0.14

 Dspace 1.7.1

 JDK 6 update 26

 Postgresql 9.0.4-1

 I succeeded in installing the components up to the  command mvn package.
 When I try ant fresh_install i am getting some errors. Which I have
 saved as a doc. file and attached along with for your perusal and
 suggestions. I am also furnishing the last few lines of the error here
 for your ready reference.

 load_registries:

 [java] 2011-09-13 16:12:49,296 INFOorg.dspace.core.ConfigurationManager
 @ Loading system provided config property (-Ddspace.configuration):
 config/dspace.cfg

 [java] 2011-09-13 16:12:49,296 INFOorg.dspace.core.ConfigurationManager
 @ Using default log4j provided log configuration,if unintended, check
 your dspace.cfg for (log.init.config)

 [java] 2011-09-13 16:12:49,703 INFOorg.dspace.content.BitstreamFormat @
 anonymous::create_bitstream_format:bitstream_format_id=80

 [java] 2011-09-13 16:12:49,703 INFOorg.dspace.content.BitstreamFormat @
 anonymous::update_bitstream_format:bitstream_format_id=80

 [java] 2011-09-13 16:12:49,703 FATAL
 org.dspace.administer.RegistryLoader @ anonymous::error_loading_registries:

 [java] org.postgresql.util.PSQLException: ERROR: duplicate key value
 violates unique constraint bitstreamformatregistry_short_description_key

 [java]Detail: Key (short_description)=(Unknown) already exists.

 [java]at
 org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:1531)

 [java]at
 org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1313)

 [java]at
 org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:188)

 [java]at
 org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:452)

 [java]at
 org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:354)

 [java]at
 org.postgresql.jdbc2.AbstractJdbc2Statement.executeUpdate(AbstractJdbc2Statement.java:308)

 [java]at
 org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)

 [java]at
 org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)

 [java]at
 org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)

 [java]at
 org.dspace.storage.rdbms.DatabaseManager.executeUpdate(DatabaseManager.java:1315)

 [java]at
 org.dspace.storage.rdbms.DatabaseManager.update(DatabaseManager.java:729)

 [java]at org.dspace.content.BitstreamFormat.update(BitstreamFormat.java:601)

 [java]at
 org.dspace.administer.RegistryLoader.loadFormat(RegistryLoader.java:183)

 [java]at
 org.dspace.administer.RegistryLoader.loadBitstreamFormats(RegistryLoader.java:138)

 [java]at org.dspace.administer.RegistryLoader.main(RegistryLoader.java:75)

 [java] Error:

 [java]- ERROR: duplicate key value violates unique constraint
 bitstreamformatregistry_short_description_key

 [java]Detail: Key (short_description)=(Unknown) already exists.

 BUILD FAILED

 C:\dspace\dspace-1.7.1-src-release\dspace\target\dspace-1.7.1-build.dir\build.xm

 l:809: Java returned: 1


 Please help me resolve this issue.

 thanks,


 --
 All the data continuously generated in your IT infrastructure contains a
 definitive record of customers, application performance, security
 threats, fraudulent activity and more. Splunk takes this data and makes
 sense of it. Business sense. IT sense. Common sense.
 http://p.sf.net/sfu/splunk-d2dcopy1



 ___
 Dspace-general mailing list
 Dspace-general@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-general

--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes

[Dspace-general] Final days of DSpace 1.8.0 Testathon : Sept 12-23

2011-09-22 Thread Tim Donohue
Hello all,

Just a reminder that today  tomorrow are our final days of the official 
1.8 Testathon. If you haven't had a chance to help us test 1.8.0, we'd 
encourage you to take a few minutes to browse around and see what you think!

More details on how you can help are posted at:
https://wiki.duraspace.org/display/DSPACE/DSpace+Release+1.8.0+Testathon+Page

A full list of features/changes in DSpace 1.8.0 can be found at:
https://wiki.duraspace.org/display/DSPACE/DSpace+Release+1.8.0+Notes

Even after Testathon completes, our main Demo Server 
(http://demo.dspace.org) will still remain available for last-minute 
testing. So, you are welcome to continue to perform a bit of testing 
next week. However, we encourage you to report any issues you've located 
as soon as possible, so that we can get any final bugs resolved before 
the 1.8.0 final release.

Thanks to all of you who have already helped test  reported issues!  We 
really depend on your support to help ensure the release is as bug-free 
as possible.

We're looking forward to an exciting 1.8.0 release in October (see 
release notes above for our tentative release schedule).

- The DSpace Committers

On 9/7/2011 4:48 PM, Tim Donohue wrote:
 DSpace Community,

 On behalf of the DSpace Committers, we'd like to formally announce the
 DSpace 1.8.0 Testathon will begin on Monday, September 12 and last until
 Friday, September 23.

 This is your opportunity to get a preview of the upcoming 1.8.0 release,
 while also helping us to fully test the system and squash any last bugs!

 During the Testathon (September 12-23), you can help us by testing an
 early version of 1.8.0 on our Demo Site (http://demo.dspace.org) or
 other available Testathon sites (TBA).

 If you are technically inclined, next week you may also download a copy
 of this early release (1.8.0 RC1) and install it on your own local
 development server:
 https://sourceforge.net/projects/dspace/files/DSpace%20Release%20Candidate/

 Some key 1.8.0 features to be on the lookout for include:
 * Configurable Reviewer Workflow - adds ability to configure your own
 local approval workflow processes
 * Media RSS Feeds - Allows DSpace media content to now be published to
 iTunes U, iTunes podcasts, etc.
 * A SWORD Client - allows DSpace to send its content (via SWORD) to
 another SWORD enabled repository (including another DSpace)
 * Reordering of Bitstreams - Allows you to reorganize the files attached
 to an item into a defined order.
 * Virus checking during Submission process - when enabled, allows you to
 virus check all files *before* they get into DSpace.
 * Compatibility with SWORD v2 protocol - allows SWORD 2 clients to
 submit packages to DSpace.
 * Rewrite of Creative Commons Licensing - improves the process for
 adding a CC License to content during the submission process.
 * Split up the 'dspace.cfg' file into smaller, more easily managed
 configuration files.
 * Numerous other features, improvements  bug fixes

 A full list of features/changes in DSpace 1.8.0 can be found at:
 https://wiki.duraspace.org/display/DSPACE/DSpace+Release+1.8.0+Notes

 For additional information on the Testathon, how you can help, and how
 you can provide feedback, please visit:
 https://wiki.duraspace.org/display/DSPACE/DSpace+Release+1.8.0+Testathon+Page


 Thanks! We hope you enjoy your preview of 1.8.0 next week! Don't
 hesitate to get in touch with any feedback!


--
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] Announcement: Another Successful Google Summer of Code!

2011-09-28 Thread Tim Donohue
All,

As we head into Fall (for those of us in the Northern Hemisphere), we 
thought it appropriate to reflect back on the successes that came out of 
this year's Google Summer of Code (GSoC - http://code.google.com/soc/).

As you may recall, this is the first year that all DuraSpace projects 
took part in GSoC, with Fedora  DuraCloud joining DSpace with a project 
apiece.

This year we had a great group of students and mentors that resulted in 
a total of five successful GSoC projects!

Submission Enhancements in DSpace - Gaurav Kejriwal

(Mentored by Mark Diggory  Scott Phillips)

Gaurav's project sought to ease the ability of repository managers to 
customize the DSpace submission process. The goal was to allow 
Administrative users to configure the DSpace submission process from the 
administration user interface. The overarching idea is to replace the 
existing XML based configuration files (item-submission.xml and 
input-forms.xml) with a database-driven user interface. During the 
summer, Gaurav worked to replace the existing 'item-submission.xml' 
configuration file. With guidance from his mentors, Gaurav designed a 
new database-driven architecture, mocked up  built a new Submission 
Administrative UI (for XMLUI), and delivered a final code patch to the 
Committers. His work is under review in our JIRA Issue Tracker, and we 
hope that it will be added to a future version of DSpace.

For more on this project, screenshots and code, see: 
https://wiki.duraspace.org/display/GSOC/GSoC+2011+-+DSpace+Submission+Enhancements


Migrate to a modern Web service library for SOAP and support MTOM 
(Fedora) - Jiri Kremser

(Mentored by Adam Soroka)

Jiri worked on updates to Fedora to use Apache CXF for the SOAP exposure 
of Fedora's web service APIs. Fedora was formerly using an older web 
service library that had significant limitations. Jiri's changes will 
allow developers to integrate their software more easily, and in more 
familiar ways. His work is currently being tested and merged into the 
main line of development, and the committers hope to include it in 
Fedora 3.6, scheduled for late 2011.

For more on this project, see: 
https://wiki.duraspace.org/display/GSOC/GSoC+2011+-+Fedora+Web+Services+Update


Eucalyptus Integration (DuraCloud) - Rajender Naik

(Mentored by Bill Branan  Andrew Woods)

Rajender's project focused on the creation of a storage provider 
implementation for the Eucalyptus Walrus cloud storage system. This new 
storage provider would allow for the integration of private clouds 
(running Walrus) with the public cloud systems that are currently 
available through DuraCloud. These hybrid clouds (which combine public 
and private cloud systems) provide an ideal solution for organizations 
that would like to combine the convenience and flexibility of the cloud 
with the security and predictability of in-house data centers. 
Rajender's work over the summer created a baseline implementation which 
can connect to a Walrus system and perform most basic storage functions. 
While more work is needed for this work to be included in the formal 
DuraCloud baseline, Rajender is still engaged and working to see this 
new storage provider become a part of DuraCloud in an upcoming release.

For more on this project, see: 
https://wiki.duraspace.org/display/GSOC/DuraCloud+-+Eucalyptus+Project


New UI built over RESTful services (DSpace) - Vibhaj Rajan

(Mentored by Bojan Suzic  Mark Diggory)

Vibhaj investigated building one of the first user interfaces on top of 
the beta DSpace REST API 
(https://wiki.duraspace.org/display/DSPACE/REST+API). His goal was to 
build a lightweight, theme-able, Javascript user interface, that could 
perform all normal DSpace activities via the REST API (some features are 
still a work in progress). Vibhaj's Javascript interface is powered by 
JQuery UI (http://jqueryui.com/) and a new FireSpark service computing 
platform (also built on JQuery). In addition, the project provides great 
examples of how DSpace may leverage JQuery (and similar technologies) to 
build even more dynamic and flashy interfaces. We hope to see Vibhaj's 
hard work updated  maintained alongside the REST API.

For more on this project, screenshots and code, see: 
https://wiki.duraspace.org/display/GSOC/DSpace+ClientUI+built+on+RESTful+API+-+GSoC+2011


WebMVC (Freemarker) UI development (DSpace) - Robert Qin Zhengquan

(Mentored by Graham Triggs, Peter Dietz,  Stuart Lewis)

Robert concentrated on enhancing the new WebMVC (Freemarker) User 
Interface work (begun by Graham Triggs), a project which seeks to 
potentially update/replace the aging JSPUI. Robert's GSoC project 
centered around adding administrative functionality to the new 

Re: [Dspace-general] subscribe to Handle system

2012-01-23 Thread Tim Donohue
Hi Nisreen,

DSpace doesn't manage the Handle system. If you have questions about the 
Handle System, you should get in touch with their support team.

Their contact information is available at:

http://handle.net/support.html

- Tim

On 1/23/2012 10:25 AM, Nisreen Kabani wrote:
 *Good Day,
 *

 I amstudent at DamascusUniversity, and haveset up a digital repository
 for the University of Damascus, and now we want to subscribe toHandle
 system.

   Due to the laws of the University of Damascus, we can not pay for the
 subscriptionby credit card, so please notify us by any other ways
 available for subscription,
   and whether They have  any agents here in Syria.

 Best regards,


 --
 *Nisreen kabani
 *Master student
 University of Damascus



 --
 Try before you buy = See our experts in action!
 The most comprehensive online learning library for Microsoft developers
 is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
 Metro Style Apps, more. Free future releases when you subscribe now!
 http://p.sf.net/sfu/learndevnow-dev2



 ___
 Dspace-general mailing list
 Dspace-general@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-general

--
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] Fwd: Google Scholar discoverability of repository content

2012-02-17 Thread Tim Donohue
Hi All,

I had sent this response on to the 'JISC-REPOSITORIES' list where this 
'Google Scholar discoverability' thread began. This info is more 
specific to DSpace users:

As of DSpace 1.7.0 (released Dec 2010), DSpace ships with Google Scholar 
recommended metadata enabled out-of-the-box.

For that release, DSpace developers at MIT actually worked directly
with the technology lead for Google Scholar to ensure DSpace content
could be more discoverable via Google Scholar.

However, it is worth noting that institutions may need to modify the
configuration of the DSpace Google Scholar mappings if they have
customized their local DSpace metadata schema in any way. Those
instructions are in our DSpace Documentation at:
https://wiki.duraspace.org/display/DSDOC18/Google+Scholar+Metadata+Mappings

DSpace also provides general hints/tips on ensuring that your
institutions' DSpace installation is indexed/discoverable via Google
(and other search engines) in general. Many of these tips were
actually written/provided by Robert Tansley at Google (initial creator
of DSpace).

https://wiki.duraspace.org/display/DSPACE/Ensuring+your+instance+is+indexed

- Tim

-- 
Tim Donohue
Technical Lead for DSpace Project
DuraSpace.org


On 2/17/2012 6:40 AM, Stevan Harnad wrote:
 Important feedback from Tim Brody, one of the developers of EPrints:

 Begin forwarded message:

 *From: *Tim Brody t...@ecs.soton.ac.uk mailto:t...@ecs.soton.ac.uk
 *Date: *February 17, 2012 6:33:22 AM EST
 *To: *eprints-t...@ecs.soton.ac.uk mailto:eprints-t...@ecs.soton.ac.uk
 *Cc: *jisc-repositor...@jiscmail.ac.uk
 mailto:jisc-repositor...@jiscmail.ac.uk
 *Subject: **[EP-tech] Re: Google Scholar discoverability of repository
 content*
 **

 Hi All,

 Here is some specific advice for existing repository administrators from
 Google Scholar:
 http://roar.eprints.org/help/google_scholar.html

 As far as I'm aware there isn't anyone running EPrints 2 now, so
 EPrints-based repositories are already (and for a long) the best in
 class for Google Scholar.


 Right, this paper ...

 Table 1 is irrelevant and misleading. Scholar links first to the
 publisher and, only if there is no publisher link, directly to the IR
 version. That's a policy decision on the part of Scholar and nothing to
 do with IRs.

 Table 2 gives us some useful data. The headline rate for EPrints is 88%
 (based on CalTech). Unfortunately the authors haven't provided an
 analysis of what happened to the missing records. I've done a quick
 random sample of CalTech and I suspect the missing records will consist
 of:
 1) Non-OA/non-full-text records (I'm sure a query to the CalTech
 repository admin could supply the data).
 2) A percentage of PDFs that Scholar won't be able to parse. CalTech
 contains some old (1950s), scanned PDFs from Journals. Where the article
 isn't at the top of the page Scholar will struggle to parse the
 title/authors/abstract and therefore won't be able to match it to their
 records e.g. http://authors.library.caltech.edu/5815/


 The remainder of the paper describes the authors' process of fixing
 their own IR (based on CONTENTdm).


 The authors then wrongly conclude:

 Despite GS’s endorsement of three software packages, the surveys
 conducted for this paper demonstrates that software is not a deciding
 factor for indexing ratio in GS. Each of the three recommended software
 packages showed good indexing ratios for some repositories and poor
 ratios for others.

 The authors looked at one instance of EPrints and, despite being a
 relatively old version, found 88% of its records indexed in GS.

 It is unfortunate that this paper has suggested that IR software in
 general is poorly indexed in GS. On the contrary, some badly implemented
 IR software is poorly indexed in GS.


 After all that is said, the most critical factor to IR visibility is
 having (BOAI definition) open access content. Hiding content behind
 search forms, click-throughs and other things that emphasise the IR at
 the expense of the content will hurt your visibility.

 Lastly, Google will index your metadata-only records while Google
 Scholar is looking for full-texts. Your GS/Google ratio will approximate
 how many of your records have an attached open access PDF (.doc etc).


 Sincerely,
 Tim Brody
 (EPrints Developer)

 On Wed, 2012-02-15 at 11:31 +, Stevan Harnad wrote:
 Can we enhance the google-scholar discoverability of EPrints (and
 DSpace) repositories?

 http://linksource.ebsco.com/linking.aspx?sid=googleauinit=Kaulast=Arlitschatitle=Invisible+Institutional+Repositories:+Addressing+the+Low+Indexing+Ratios+of+IRs+in+Google+Scholartitle=Library+Hi+Techvolume=30issue=1date=2012spage=4issn=0737-8831
 http://linksource.ebsco.com/linking.aspx?sid=googleauinit=Kaulast=Arlitschatitle=Invisible+Institutional+Repositories:+Addressing+the+Low+Indexing+Ratios+of+IRs+in+Google+Scholartitle=Library+Hi+Techvolume=30issue=1date=2012spage=4issn=0737-8831

 Kenning Arlitsch, Patrick Shawn OBrien

[Dspace-general] DSpace 1.8.2 Released - provides bug fixes to 1.8.x platform

2012-02-24 Thread Tim Donohue
Hello DSpace Community,

We have a new bug-fix release of DSpace 1.8 available: DSpace 1.8.2

This small bug fix release addresses a number of issues that have 
cropped up since 1.8.0 and 1.8.1. These issues include:
* Several bug fixes to the AIP Backup  Restore tools
* Increase default XMLUI upload limit to 2GB max
* Fix issue with concurrent workflow task claiming in XMLUI
* Additional bug fixes to Discovery  XMLUI

A full list of the resolved issues can be found at:
https://wiki.duraspace.org/display/DSPACE/DSpace+Release+1.8.2+Notes

Although this upgrade only provides a small number of bug fixes, we 
recommend that anyone using the AIP Backup  Restore tools upgrade to 
1.8.2. Additionally, anyone who wants to take advantage of other small 
fixes to Discovery or XMLUI may also wish to perform this upgrade.

Installation and Upgrade Instructions
* Installation: https://wiki.duraspace.org/display/DSDOC18/Installation
* Upgrade: 
https://wiki.duraspace.org/display/DSDOC18/Upgrading+a+DSpace+Installation

Obtaining DSpace
* Download Release: https://sourceforge.net/projects/dspace/
* Checkout via Source Control (SVN): 
http://scm.dspace.org/svn/repo/dspace/tags/dspace-1.8.2/

DSpace would not exist without the hard work and support of the 
community! We'd like to thank each of you for continuing to use DSpace, 
test DSpace, and provide feedback to the developers.

Tim Donohue
Technical Lead for DSpace Project
DuraSpace.org

--
Virtualization  Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] [Dspace-devel] (no subject)

2012-03-05 Thread Tim Donohue
Hi,

Currently, no. The Mirage theme is only available for XMLUI. The older 
JSPUI does not support themes.

There is a prototype WebMVC UI project which also allows themes (such as 
Mirage). But it is still in early development stages, and as far as I'm 
aware is not used in production anywhere. 
https://wiki.duraspace.org/display/DSPACE/WebMVC+%28Freemarker%29+UI

- Tim

On 3/3/2012 6:35 AM, Nisreen Kabani wrote:
 Is it possible the application of Mirage on the front jspui؟


--
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] Announcing DSpace 3.0 and Changes to DSpace Release Numbering

2012-03-12 Thread Tim Donohue
All,

On behalf of the DSpace Committers, I'd like to formally announce a change to 
the DSpace Release Numbering Scheme, as well as the upcoming 3.0 release.
(This announcement is also available online at: 
http://duraspace.org/announcing-dspace-30-and-changes-dspace-release-numbering)

In the past, we have had a three-tiered numbering scheme 
([major].[minor].[subminor]), e.g. 1.8.0, 1.8.1, 1.8.2. However, over the 
years, we've heard feedback that this numbering scheme could be confusing, as 
it was unclear which releases contained brand new features and which releases 
only contained bug fixes.

Therefore, we've decided to simplify our release numbering scheme to just two 
numbers.

== New DSpace Release Numbering Scheme ==

'[major].[minor]' (e.g. 3.0, 3.1, 3.2)

This new numbering scheme will be used as follows:

* Major Releases: incrementing the first number ('major') will represent a new 
MAJOR release of DSpace.  A major release may include any or all of the 
following: new features, system improvements, architectural changes, bug fixes. 
All major releases end in .0, so 3.0, 4.0, and 5.0 would all represent 
major releases.

* Minor Releases: incrementing the second number ('minor') will represent a new 
MINOR release of DSpace. A minor release will *only include* bug fixes to an 
existing major release. For example, 3.1 and 3.2 would represent two minor 
releases which only include bug fixes to the 3.0 major release.

== DSpace 3.0 : Fall 2012 ==

As a related announcement, the DSpace Committers would like to announce that in 
Fall 2012 we will be releasing DSpace 3.0. This release is tentatively 
scheduled for October or November of this year.

DSpace 3.0 will be the next major release of the platform. It will immediately 
follow the 1.8.x releases, providing new features/improvements/fixes to the 
existing DSpace platform. We are in the early planning process for 3.0 
features, but you can follow along on the 3.0 Release Notes page:
https://wiki.duraspace.org/display/DSPACE/DSpace+Release+3.0+Notes

The DSpace Committers will continue to strive to release one major version of 
DSpace each year, followed by any necessary minor releases (to fix any bugs 
that may be found). Per our new Release Numbering Scheme, after 3.0 is released 
in late 2012, we plan to release 4.0 in late 2013, 5.0 in late 2014, etc.

== What happened to DSpace 2.0? == 

Some may be wondering what has happened to the often talked about DSpace 2.0? 
After much discussion, the Committers along with members of the DSpace 
Community Advisory Team (DCAT) have decided to forgo releasing a DSpace 2.0. 

The reasons for this decision were numerous and include:
* The vision of DSpace 2.0 has gone through many different lists of proposed 
features over the past 8 years:
   - Discussion of 2.0 first began in 2004, with Robert Tansley's original 
proposal for a 2.0 release
   - A reworking of the 2.0 concept happened in 2006, during a DSpace 
Architectural Review
   - A further reworking of the 2.0 concept occurred in 2008-2009 when a 
prototype version of DSpace 2.0 was built and demoed at Open Repositories 2009 
(https://wiki.duraspace.org/display/DSPACE/DSpace+2.0)
* As detailed above, much of the planning around a 2.0 is now many years old. 
Although great ideas/concepts have come out of that work, much of it does need 
to be reanalyzed for the modern repository environment.
* 2.0 has always been talked about as a revolutionary change to the DSpace 
software platform.  In reality, we've found that many of these platform 
improvements have been incremental in nature and have been included over many 
releases (for example, nearly every major release in recent years has included 
some code/concepts from the 2009 DSpace 2.0 Prototype).
* Because the 2.0 release has a perception of being revolutionary in nature, 
it would be difficult to ever fully meet the expectations/assumptions that have 
built up around this release over time.
* We all feel that the DSpace Community's immediate needs are better met by 
incremental changes (over several releases) than by revolutionary changes (over 
a single release). We feel that incremental changes provide an easier upgrade 
path between current and future releases of DSpace.

Therefore, many of the ideas/concepts of DSpace 2.0 may still be coming to 
the modern DSpace platform. But, they will continue to be added incrementally 
over several releases. The ideas behind 2.0 still live on, even while the 
DSpace release numbering has changed.

For more information about 3.0 or the decisions around forgoing a 2.0 release, 
see:
https://wiki.duraspace.org/display/DSPACE/DSpace+Release+3.0+Notes

--
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future 

[Dspace-general] NOTICE: DSpace code is now on GitHub!

2012-05-09 Thread Tim Donohue
All,

This mostly affects the DSpace developers out there (who should already 
be aware of this change via discussions on the dspace-devel listserv). 
But I wanted to be sure to send a notification to all DSpace mailing lists.

As of late April, the primary DSpace codebase has migrated to GitHub: 
https://github.com/DSpace/DSpace
All future DSpace development will take place on GitHub.

After holding a public vote (on dspace-devel) in February/March, the 
DSpace Committers and Developers unanimously voted to migrate our 
codebase from Subversion (SVN) to GitHub. We all feel that GitHub will 
provide us with ways to more easily take advantage of community-wide 
customizations / enhancements / bug fixes. It should also allow 
individual institutions to more easily share code/customizations amongst 
themselves.

All past DSpace releases (1.0 through 1.8.2) have been migrated to 
GitHub as well: https://github.com/DSpace/DSpace/tags

The old Subversion code repository is still available as a READ-ONLY 
historical archive. No more changes/commits will be made to this SVN 
codebase in the future.

SVN archive: https://svn.duraspace.org/dspace/  (Note: this is the new 
location of http://scm.dspace.org/ and all old SVN URLs should now 
redirect here.)

If your institution still prefers to use Subversion (SVN) locally, there 
are ways you can continue to use SVN instead of using Git/GitHub:
* GitHub does have some basic SVN client support: 
https://github.com/blog/966-improved-subversion-client-support (This 
allows you to checkout code stored in GitHub via SVN calls)
* Or, you could obviously download the zipped up DSpace release packages 
(from SourceForge or GitHub) and import them into your institution's 
local Subversion repository.

Finally, we are still working to update our Wiki pages  Documentation 
to reflect that GitHub is now the primary codebase (if you'd like to 
help, please feel free to chip in or get in touch via dspace-devel).

There are a few key pages that everyone should be aware of, especially 
for those new to GitHub:
* We are working on some Git/GitHub Development Best Practices at: 
https://wiki.duraspace.org/display/DSPACE/Development+with+Git  This 
page is also a good resource for those who wish to learn Git or GitHub.
* Our Developer Guidelines  Tools page is also receiving updates 
based on GitHub: 
https://wiki.duraspace.org/display/DSPACE/Developer+Guidelines+and+Tools

If you have any questions, please feel free to ask us!

- Tim

-- 
Tim Donohue
Technical Lead for DSpace Project
DuraSpace.org

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] Welcome to the latest DSpace committer: Ivan Masár (aka helix84)

2012-06-13 Thread Tim Donohue
Dear DSpace Community,

The DSpace Committers Team is delighted to announce a new member to the group: 
Ivan Masár, also known as helix84. Please join us in welcoming him!

Many of you will immediately recognize Ivan's pseudonym helix84. As helix84, 
Ivan has been a very active participant on our mailing lists, frequently 
answering questions and offering his expertise and advice to all community 
members. In recent months, Ivan has also been active in helping to resolve 
outstanding bugs and sharing his brainstorms/opinions in our weekly DSpace 
developer meetings.

Ivan has been working on DSpace since version 1.5, mainly interested in the 
XMLUI interface. His first contribution to DSpace was a translation. He's been 
maintaining two production repositories and over time gained practical 
experience which he gladly shares by improving documentation and answering 
questions of other users on the mailing lists. He has also submitted several 
patches back to DSpace based on his local repository customizations and 
improvements.

Ivan comments on his contributions: I don't consider myself a Java programmer 
by any means, but there are still many other areas where I can help out. I'm 
quite fond of XMLUI, because it allows users trying to customize DSpace great 
flexibility, so if someone asks this kind of question, I'm usually able to 
help. I'm also trying to help out by testing patches in Jira and giving 
feedback - all users who care about features in the next version should really 
get more involved in this.

Ivan comments on his invitation to become a Committer: I was quite surprised 
at first, because I didn't know I was nominated. I appreciate the trust of 
other committers. I don't think this will change what areas I'm involved in, 
for example it won't improve my Java-fu overnight, but it might speed up 
getting my patches in and I'll review other patches from Jira. I already have 
some ideas for minor XMLUI improvements in mind.

We are always on the lookout for new developers, contributors, and committers 
within the DSpace community. Anyone who would like to get more involved is 
encouraged to do so. You are also welcome to contact us at any time if you'd 
like some ideas of how to start contributing:

- https://wiki.duraspace.org/display/DSPACE/DSpaceContributors

Contributions can take many forms, from writing code to editing documentation, 
or testing new releases to designing new themes for our user interfaces.

If you or someone you know has been an active DSpace contributor for some time, 
you can also nominate that person to become our next Committer! Nomination 
details are available at:

- https://wiki.duraspace.org/display/DSPACE/Committer+Nominations

Welcome Ivan (aka helix84)!

Sincerely,

The DSpace Committers Team

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] [Dspace-tech] A question about Mirage theme

2012-06-27 Thread Tim Donohue
Hi revskill,

I'm not sure I understand the question. There actually is no tags called 
either ds-body or ds-options-wrapper in the DRI XML.

Instead, the DRI XML has a tags called dri:body and dri:options.

There are however an HTML div tags in the Mirage Theme that looks like:

div id=ds-body
div id=ds-options-wrapper

This HTML tag is generated by the Mirage Theme itself. So, I'm assuming 
you must be talking about the final HTML source rather than the DRI.

However, in the HTML source on the DSpace Demo Site 
(http://demo.dspace.org), which uses the Mirage Theme, I don't see the 
issue you mention.

In the Homepage's HTML source, I see that there are two div's that are 
at equal level:

div id=ds-body.../div
div id=ds-options-wrapper.../div

However, when viewing the HTML source of an Item page, I see those two 
div's are *still* at an equal level.

Could you send the list more information about where you see this issue? 
Or perhaps send us direct links to your DSpace site, or to an example on 
the Demo site?

Thanks!

- Tim

On 6/27/2012 4:39 AM, revskill wrote:
 Good morning. I have a problem with Mirage theme.

 As we know, the DRI format is:
 document
 body/body
 options/options
 meta/meta
 /document

 We have page-structure.xsl and navigations.xsl to generate html content
 of body and options. The strage thing here is when i browse to a
 specific item, the ds-options-wrapper (generated for dri:options) is
 nested inside the ds-body tag. But if i get the DRI of home page, the
 ds-options-wrapper is in equal level with ds-body tag.

 Please help .

 Thank you very much.

 --
 TRUONG HOANG DUNG*
 */*Librarian **Researcher
 *//Information and Library Centre
 Mobile: 0121.411.5322
 Email: _dun...@hpu.edu.vn mailto:dun...@hpu.edu.vn_/
 _/Hai Phong Private University/_ http://lib.hpu.vn


 --
 Live Security Virtual Conference
 Exclusive live event will cover all the ways today's security and
 threat landscape has changed and how IT managers can respond. Discussions
 will include endpoint security, mobile security and the latest in malware
 threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/



 ___
 DSpace-tech mailing list
 dspace-t...@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-tech



--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] XMLUI display errors

2012-06-28 Thread Tim Donohue
Hi Hilton,

It looks as though when you upgraded to 1.8.2 you may not have upgraded 
your messages.xml file (by adding all the new message keys)

So, currently you are seeing all the keys that are missing in your 
existing messages.xml file.  To get rid of those oddities, you'll need 
to update your custom messages.xml file to include all the new keys that 
were added in 1.8.0.

- Tim

On 6/28/2012 7:06 AM, Hilton Gibson wrote:
 Hi All

 See attached. These errors happen when I click on Submissions after login.
 Using Ubuntu 12.04 LTS with DSpace version 1.8.2 on our test
 and development server.
 Also the list formatting is way off and not inside the box.

 Does anyone else get them?

 Cheers

 hg

 --
 *Hilton Gibson*
 Systems Administrator
 JS Gericke Library
 Room 1025D
 Stellenbosch University
 Private Bag X5036
 Stellenbosch
 7599
 South Africa

 Tel: +27 21 808 4100 | Cell: +27 84 646 4758
 http://www.sun.ac.za/library



 --
 Live Security Virtual Conference
 Exclusive live event will cover all the ways today's security and
 threat landscape has changed and how IT managers can respond. Discussions
 will include endpoint security, mobile security and the latest in malware
 threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/



 ___
 Dspace-general mailing list
 Dspace-general@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-general



--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] NOTICE: JIRA Issue Tracker Maintenance TODAY from 4-4:30PM ET

2012-08-30 Thread Tim Donohue
All,

DuraSpace will be performing maintenance  upgrading our JIRA Issue 
Tracker today (Thurs, Aug 30) from 4-4:30PM ET. To see the corresponding 
maintenance time in your area, visit:

http://www.timeanddate.com/worldclock/fixedtime.html?msg=DuraSpace+JIRA+Maintenanceiso=20120830T20am=30

This maintenance has been necessitated by several critical security 
issues within our current version of Atlassian JIRA.

During this maintenance window the http://jira.duraspace.org site will 
be unavailable to all users.

We apologize for any inconvenience this may cause. Please feel free to 
email sysad...@duraspace.org if you have any questions or concerns.

Sincerely,

Tim Donohue (on behalf of sysad...@duraspace.org)

-- 
Tim Donohue
Technical Lead for DSpace Project
DuraSpace.org

--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] NOTICE: DuraSpace Wiki Upgrade/Downtime on Fri @ 2-3pm EDT

2012-09-26 Thread Tim Donohue
DSpace Users  Developers,

We wanted to inform you that we will be performing an upgrade of our 
DuraSpace Wiki (http://wiki.duraspace.org) on:

Friday, September 28 from 2:00pm - 3:00pm EDT (18:00 - 19:00 UTC)

During this period, all areas of the Wiki will be UNAVAILABLE for 
reading or editing.

The purpose of this upgrade is to update us to the latest and greatest 
version of Atlassian Confluence (version 4.3.1).

This upgrade will bring with it one significant change and also add many 
new features to our DuraSpace Wiki. See below for more details.


== Significant Change: No More Wiki Markup Editor ==

With Confluence 4.x, Atlassian decided to move all editing over to their 
brand new (and vastly improved) Rich Text Editor. You are still able 
to type Wiki Markup into the Rich Text editor. But, editing an existing 
page via the Wiki Markup Editor is no longer possible.

More info for the Techies: The underlying format which Confluence uses 
to store its pages has changed to XHTML from Wiki Markup. You will still 
have the ability to directly edit a page's XHTML if you desire, but the 
old Wiki Markup editor no longer exists.


== Many New Confluence Features Available ==

With this upgrade, we will now have the latest Confluence (4.3) features 
available in our DuraSpace Wiki (wiki.duraspace.org).

The new features you may notice include:

* Brand New / Enhanced Rich Text Editor. This editor is now much 
easier to use and includes enhanced table editing, easy page layouts, 
Find  Replace functionality, and auto-embedding media via a pasted in 
URL. (Added in Confluence 4.0 and enhanced in 4.1  4.2)

* Like button  Quick Commenting.  Each page  comments now have a 
Like button (similar to Facebook) which lets you add quick 
approval/thumbs up. There is now a quick comment box at the bottom of 
each page. (Added in Confluence 4.2)

* Social @mentions. Similar to Twitter or Facebook, if you type @ into 
a page/comment you can specifically mention another user to draw their 
attention to a particular page or comment. (Added in Confluence 4.0)

* Tasks  Notifications. You can create public or personal task lists 
and assign tasks to yourself or others. In addition, there's a new Wiki 
notification inbox which holds all your recent notifications or 
mentions. These notifications can also still be sent via email. (Added 
in Confluence 4.3)

* Mobile Interface. If you cannot get enough of the Wiki, there's now a 
mobile-friendly interface for making changes on the go. (Added in 
Confluence 4.3)

If you want further information about any of these features, please see 
the Confluence Release Notes:
* What's new in Confluence 4.0:
http://www.atlassian.com/software/confluence/whats-new/confluence-40
* What's new in Confluence 4.1: 
http://www.atlassian.com/software/confluence/whats-new/confluence-41
* What's new in Confluence 4.2: 
http://www.atlassian.com/software/confluence/whats-new/confluence-42
* What's new in Confluence 4.3: 
http://www.atlassian.com/software/confluence/whats-new/confluence-43

---

We hope that you find these new Wiki features  changes to be 
worthwhile. If you have any questions or concerns, please feel free to 
email sysad...@duraspace.org and we'll do our best to address them.

Sincerely,

Your friendly DuraSpace SysAdmins
sysad...@duraspace.org

--
How fast is your code?
3 out of 4 devs don\\\'t know how their code performs in production.
Find out how slow your code is with AppDynamics Lite.
http://ad.doubleclick.net/clk;262219672;13503038;z?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] DSpace-CRIS, visualizations

2012-11-09 Thread Tim Donohue
Hi All,

First off, I wanted to state that this DSpace-CRIS work done by HKU and 
CILEA all sounds very interesting. I'm looking forward to seeing the 
code when it is released to their GitHub.

In case there were any misunderstandings around the previous email, 
nearly all of the DSpace-CRIS functionality will unfortunately not be 
available in the upcoming DSpace 3.0 release. Although, one minor 
exception is that CILEA has contributed the basic JSPUI Faceted Search 
functionality for DSpace 3.0. This new functionality will essentially 
allow users to run the DSpace Discovery search engine (based on Apache 
Solr) in either XMLUI or JSPUI (previously it was only available in the 
XMLUI).

That all being said, I know the Committers (and DuraSpace) are hopeful 
that we can see many of these DSpace-CRIS features made available in a 
future version of DSpace (whether out-of-the-box or as optional 
add-ons). Having talked with folks at CILEA, I know that there is hope 
to make DSpace-CRIS compatible with DSpace 3.0 sometime in early 2013. 
So, it seems likely that the updated DSpace-CRIS code may be submitted 
for approval before our DSpace 4.0 submission deadlines next year 
(likely to be sometime in Aug/Sept 2013).

== General Reminder about DSpace Code Contributions ==

As a general reminder, if you or your institution has been doing some 
interesting customization work with DSpace, you are more than welcome to 
submit your code for approval in a future release. These submissions can 
be made at any time throughout the year. However, the Committers 
obviously must set submission deadlines around each new release (to 
ensure we have enough time to review existing submissions and also merge 
and stabilize all accepted code into the next release). Approval of code 
submissions takes place via a public vote, usually during our weekly 
developer meeting or on the dspace-devel mailing list. The Committers 
also try to consult with the DSpace Community Advisory Team (DCAT) to 
ensure new features are of general interest.

We do have published guidelines for how to submit your code or 
customization work:
https://wiki.duraspace.org/display/DSPACE/Code+Contribution+Guidelines

The better you are able to follow these guidelines, the more likely it 
is that we can add your work into a future release quickly! If any 
guidelines are unclear or you run into questions, let us know. We'd be 
more than happy to help clarify them. Finally, it is also worth pointing 
out that we are constantly adding new Committers (usually at a rate of a 
few per year). New Committers are voted in based on their contributions 
to the DSpace platform. So, chances are, if you submit customizations or 
new features, some day soon you may also be invited to join the group.

Please feel free to get in touch with myself or any of the Committers if 
you have any questions. You may also send an email to one of our DSpace 
mailing lists, and we'll answer your questions there.

Thanks,

Tim Donohue

-- 
Tim Donohue
Technical Lead for DSpace Project
DuraSpace.org

On 11/5/2012 1:55 AM, David Palmer wrote:
 The University of Hong Kong (HKU) and CILEA are pleased to announce new
 functionality to DSpace.  Our development work has now produced pages of
 networks, visualized and tabulated, for each of the HKU professoriate
 staff.  Examples of these are,

 http://hub.hku.hk/network/rp00789 (interactive; click on names, change
 degree of separation, etc.)

 http://hub.hku.hk/rp/rp00789/collaboration?open=tabulated

 As was announced in OR 2012, all of the new functionality in HKU’s
 institutional repository (The HKU Scholars Hub) will be made freely
 available to the DSpace Community.  This carries the mnemonic,
 DSpace-CRIS.  A roadmap for this work is at,

 https://github.com/CILEA/dspace-cris/wiki/Roadmap

 https://github.com/CILEA/dspace-cris/wiki

 Some of the new features that will appear in coming DSpace-CRIS releases
 are,

 ·Faceted Searching

 ·New objects or entities such as people, projects, departments, etc.

 ·Integrated faceted searching across all entities (publication items,
 people, projects, etc)

 ·Customized browse indexes on these new entities, like publication items

 ·Interlinkage between new entities and publications

 ·New user interface to control the new entities

 ·Article level metrics (PubMed Central)

 ·Make “select list” of publications

 Best wishes,

 David Palmer


--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_nov
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] Amazon Web Services - EC2

2012-11-14 Thread Tim Donohue
The DSpace Demo site (http://demo.dspace.org) is also running on Amazon 
EC2 (Ubuntu), with no issues.

 From my experience, installing DSpace on Amazon EC2 is really not much 
different from installing it on a physical server.  So, for example, if 
you have installed DSpace on Ubuntu (or Windows) on a physical server, 
it's no different to install DSpace on Ubuntu (or Windows) in Amazon EC2.

- Tim


On 11/13/2012 6:05 PM, Bruce Jensen wrote:
 Hi folks
 Librarian + programmer Yan Han of the U of Arizona runs the Afghanistan
 Digital Collections
 http://www.afghandata.org:8080/xmlui/handle/123456789/1, a DSpace
 repository, on the Amazon ElasticCompute Cloud. Kevin Gilbertson et al.
 at Wake Forest also have their DSpace
 http://wakespace.lib.wfu.edu/jspui/ on EC2.

 Do you know of other such production use cases, or have you experimented
 with this yourself?

 Thanks!

 Bruce Jensen
 Rohrbach Library
 Kutztown University of Pennsylvania
 Tel  610-683-4766
 Txt  956-605-3176
 rjen...@kutztown.edu mailto:rjen...@kutztown.edu


 --
 Monitor your physical, virtual and cloud infrastructure from a single
 web console. Get in-depth insight into apps, servers, databases, vmware,
 SAP, cloud infrastructure, etc. Download 30-day Free Trial.
 Pricing starts from $795 for 25 servers or applications!
 http://p.sf.net/sfu/zoho_dev2dev_nov



 ___
 Dspace-general mailing list
 Dspace-general@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-general


--
Monitor your physical, virtual and cloud infrastructure from a single
web console. Get in-depth insight into apps, servers, databases, vmware,
SAP, cloud infrastructure, etc. Download 30-day Free Trial.
Pricing starts from $795 for 25 servers or applications!
http://p.sf.net/sfu/zoho_dev2dev_nov
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] DSpace scalability (tens of hundreds TBs)

2013-04-08 Thread Tim Donohue
Hi Vlastik,

Unfortunately, as far as I'm aware there are no DSpace installations 
with many TBs worth of data. (If anyone out there is running DSpace with 
large amounts of data, we'd definitely love to hear from your experiences!)

I'd hope that DSpace could scale to that level. But, to be completely 
honest, we've never had anyone attempt it. However, should you have the 
resources to do this sort of scalability testing, we'd definitely 
appreciate feedback on any issues you run into (if any).

We do our best to ensure that DSpace is scalable. But, as we are a team 
of volunteers, we don't always have the resources to do extensively 
large scalability testing (and therefore, we are forced to depend on the 
community to help report such issues to us). However, we'd do our best 
to help resolve any issues you'd encounter -- we've worked with others 
in the past when they've noticed scalability or memory leak issues in 
DSpace.

If you were to encounter issues, it'd likely be memory related issues. 
In recent releases we've done some work to plug some longer standing 
memory leaks. But, I cannot guarantee we've located them all. Again 
though, this is something we'd love feedback on -- we'd want to fix 
memory leaks as quickly as we can.

I'm not sure if that helps or not.

- Tim

On 4/4/2013 8:44 AM, Vlastimil Krejcir wrote:
 Hello all,

 I have been recently ask the question on DSpace scalability - assume the
 project:

 16 millions of items (bistreams size about 230 TB) increasing by 3
 millions items (86 TB) per year

 Is DSpace able to handle this? My answer was I don't know. Is anyone
 working with such big loads of data? What is your opinion?

 Regards,

 Vlastik

 
 Vlastimil Krejčíř
 Library and Information Centre, Institute of Computer Science
 Masaryk University, Brno, Czech Republic
 Email: krejcir (at) ics (dot) muni (dot) cz
 Phone: +420 549 49 3872
 ICQ: 163963217
 Jabber: kre...@jabber.org
 

 --
 Minimize network downtime and maximize team effectiveness.
 Reduce network management and security costs.Learn how to hire
 the most talented Cisco Certified professionals. Visit the
 Employer Resources Portal
 http://www.cisco.com/web/learning/employer_resources/index.html
 ___
 Dspace-general mailing list
 Dspace-general@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-general


--
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire 
the most talented Cisco Certified professionals. Visit the 
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] DSpace scalability (tens of hundreds TBs)

2013-04-08 Thread Tim Donohue
Hi Vlastik,

This had slipped my mind, but there was some scalability testing by U of 
Cambridge in 2010. They had tested with DSpace 1.6.2. At the time they 
ran into scalability/memory issues, when loading DSpace 1.6.2 with 12 TB 
worth of data

http://dspace.2283337.n4.nabble.com/Dspace-tech-Scalability-issues-report-DSpace-Cambridge-td3287701.html

However, based on Cambridge's reported issues, we performed many 
scalability/memory usage enhancements in DSpace 1.7.0 (and Cambridge had 
verified those resolved their issues -- cannot seem to track down that 
email though). More notes on the performance improvements in 1.7.0 are 
on our 1.7.0 Release notes:
https://wiki.duraspace.org/display/DSPACE/DSpace+Release+1.7.0+Notes

Since then, we've kept a closer watch for possible memory leaks. I 
cannot guarantee we've caught all of them, but if any are noticed, we'd 
gladly try to resolve them ASAP.

U of Cambridge is one of the larger (known) DSpace instances. I'm not 
sure how much data they currently have. But, at least in 2010 they said 
they had around 12TB (200K items).

- Tim


On 4/8/2013 9:49 AM, Tim Donohue wrote:
 Hi Vlastik,

 Unfortunately, as far as I'm aware there are no DSpace installations
 with many TBs worth of data. (If anyone out there is running DSpace with
 large amounts of data, we'd definitely love to hear from your experiences!)

 I'd hope that DSpace could scale to that level. But, to be completely
 honest, we've never had anyone attempt it. However, should you have the
 resources to do this sort of scalability testing, we'd definitely
 appreciate feedback on any issues you run into (if any).

 We do our best to ensure that DSpace is scalable. But, as we are a team
 of volunteers, we don't always have the resources to do extensively
 large scalability testing (and therefore, we are forced to depend on the
 community to help report such issues to us). However, we'd do our best
 to help resolve any issues you'd encounter -- we've worked with others
 in the past when they've noticed scalability or memory leak issues in
 DSpace.

 If you were to encounter issues, it'd likely be memory related issues.
 In recent releases we've done some work to plug some longer standing
 memory leaks. But, I cannot guarantee we've located them all. Again
 though, this is something we'd love feedback on -- we'd want to fix
 memory leaks as quickly as we can.

 I'm not sure if that helps or not.

 - Tim

 On 4/4/2013 8:44 AM, Vlastimil Krejcir wrote:
 Hello all,

 I have been recently ask the question on DSpace scalability -
 assume the
 project:

 16 millions of items (bistreams size about 230 TB) increasing by 3
 millions items (86 TB) per year

 Is DSpace able to handle this? My answer was I don't know. Is anyone
 working with such big loads of data? What is your opinion?

 Regards,

 Vlastik

 

 Vlastimil Krejčíř
 Library and Information Centre, Institute of Computer Science
 Masaryk University, Brno, Czech Republic
 Email: krejcir (at) ics (dot) muni (dot) cz
 Phone: +420 549 49 3872
 ICQ: 163963217
 Jabber: kre...@jabber.org
 


 --

 Minimize network downtime and maximize team effectiveness.
 Reduce network management and security costs.Learn how to hire
 the most talented Cisco Certified professionals. Visit the
 Employer Resources Portal
 http://www.cisco.com/web/learning/employer_resources/index.html
 ___
 Dspace-general mailing list
 Dspace-general@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-general


--
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire 
the most talented Cisco Certified professionals. Visit the 
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] DuraCloud Brown Bag Session 4/24 - Preserving DSpace Content with DuraCloud

2013-04-18 Thread Tim Donohue

  
  


  

  

  

  

  

  

  
 

  
DuraCloud
Brown Bag Series
  

  

  


   
  


   
  


  

  

  

  This Month's
  Topic: Preserving DSpace
  Content with DuraCloud
  
  TheDuraCloud team
  will host the thirdbrown bag session of
  2013 nextWednesday, April 24th
  at 12:30pm ET.April's brown bag
  session will be conducted by guest
  presenter Tim Donohue, DSpace
  Technical Lead, and will detail
  how to preserve DSpace content
  with DuraCloud. Specifically, Tim
  will give a short demonstration of
  how to backup content from a
  DSpace instance to DuraCloud via
  the replication task suite add-on.
  
  Tune in
  to the "DuraCloud Brown Bag
  Series" for short, 30-minute demonstrations
and/or discussions of new
features, common use cases, or
topics presented by guest
speakers with an additional 15
minutes reserved at the end of
each session for questions.The Brown
  Bag series takes place on the last
  Wednesday of every month from
  12:30-1:15pm ET.
  
  There
is no need to register to
attend, simply connect to the
session if you are available.
  
  
  To join
  the event:
  
Log in to
  http://educause.acms.com/duraspace/.
On the
  welcome page, click to "Enter As
  Guest" and enter your name and
  institution.
Click "Enter
  Room" and the session will launch.
  
  
  Before
  the event:
  
Audio for the
  webinar will be presented through
  your computer speakers.
Please be
  sure to run a system test before
  logging in:
  http://educause.adobeconnect.com/common/help/en/support/meeting_test.htm.
  
  
  For the
complete list of upcoming Brown Bag
topics or to submit a suggested
topic, please visit: http://duracloud.org/brown_bag_series
or contact Caris

[Dspace-general] Report from initial meeting on 3-5 year DSpace Vision

2013-05-21 Thread Tim Donohue
All,

Earlier in May, DuraSpace convened a small group of DSpace 
stakeholders/sponsors to begin brainstorming a 3-5 year Vision and High 
Level Roadmap for the DSpace platform.

We have just posted a brief summary of the discussions from this 
meeting, the outcomes and suggested next steps:
http://duraspace.org/meeting-report-3-5-year-dspace-vision

You are also welcome to read through the detailed meeting notes:
https://wiki.duraspace.org/display/DSPACE/DSpace+2013+Vision+and+Roadmap+Meeting

Based on the discussions of this meeting, we have begun to draft a 
Vision Document for DSpace. It is still very much a work in progress, 
and will be enhanced in the coming weeks/months. Therefore, please be 
warned that nothing in this early draft is finalized. But, you are more 
than welcome to take an early peek:
https://wiki.duraspace.org/display/DSPACE/DSpace+2013+Vision+Document

Much more information and many more discussions will be coming soon. In 
the meantime, you are welcome to contribute your own initial feedback 
(as a comment) to the wiki page above. We will be providing additional 
opportunities for public discussion/feedback both virtually and at Open 
Repositories 2013 (http://or2013.net/).

Finally, it is worth noting that this DSpace 3-5 year Vision discussion 
does not have any direct relationship with the DSpace 4.0 release 
scheduled for late 2013. The DSpace 4.0 Release will go forward as 
planned and will add new features/improvements to our existing platform. 
The goal of this longer term DSpace Vision discussion is to describe use 
cases for a potentially new or updated DSpace platform, which may 
require many years/releases to implement.

Feel free to let us know if there are immediate questions. We look 
forward to envisioning the future of DSpace together.

Tim Donohue
Technical Lead for DSpace
DuraSpace.org

--
Try New Relic Now  We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app,  servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] What does VIVO add to DuraSpace

2013-05-28 Thread Tim Donohue
Hi Brent,

Jonathan Markow already provided a nice overview of why DuraSpace is 
interested in helping steward the VIVO project.

One other thing to note. In your question, you seem to be implying that 
DuraSpace is a piece of software. DuraSpace is not a software product 
and it never will be.

To clarify, DuraSpace is a non-profit organization that helps support 
several open source software projects (and a few hosted services as 
well). Presently, the DuraSpace organization acts as the stewards of 
DSpace software and Fedora software products. As Jonathan mentioned, 
we've just recently begun incubation of VIVO software. Incubation 
means that we are working with the VIVO developers to help transition 
their software development processes from grant funded to community 
supported in the hopes of improving long term sustainability of the 
project. This is very similar to the Apache Foundation's 
(http://www.apache.org/) incubation processes, if you are familiar 
with those.

DuraSpace becoming stewards of VIVO software does NOT mean that DSpace 
software or Fedora software will include VIVO out-of-the-box.  However, 
obviously we'd like to encourage all of these software products to 
integrate with one another (though the various user communities will 
decide the extent of integration between these software products).

Let us know if this is still unclear. We'd be glad to clarify as needed.

- Tim

-- 
Tim Donohue
Technical Lead for DSpace
DuraSpace.org

On 5/25/2013 5:11 PM, Brent Shambaugh wrote:
 Dear all,

 Regrettably, I'm a bit confused what VIVO adds to DuraSpace. It is my
 understanding that DuraSpace presently only harvests metadata but VIVO
 allows for searching of Metadata through LOD and LD (1), (2), (?). I am
 aware of another project called Fedora supported by DuraSpace, which
 includes a repository that is more flexible than DSpace (3). In the talk
 by Jonathan Markow (4), Fedora synergy with VIVO was given as an
 example. Thank you for your time.

 Brent

 (1) http://www.duraspace.org/dspace-futures
 (2) https://wiki.duraspace.org/display/DSDOC3x/OAI+2.0+Server
 (3) http://duraspace.org/dspace_or_fedora
 (4)
 http://www.vivoweb.org/files/presentations/12Thu/DuraSpace_and_VIVO-Jonathan-Markow.pdf



 --
 Try New Relic Now  We'll Send You this Cool Shirt
 New Relic is the only SaaS-based application performance monitoring service
 that delivers powerful full stack analytics. Optimize and monitor your
 browser, app,  servers with just a few lines of code. Try New Relic
 and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may



 ___
 Dspace-general mailing list
 Dspace-general@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-general


--
Try New Relic Now  We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app,  servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] DSpace 2013 RoadMap 3-5 Year Vision

2013-07-18 Thread Tim Donohue
All,

Last week at the Open Repositories conference (in Prince Edward Island, 
Canada), a draft 3-5 Year Vision for the DSpace platform was introduced 
as well as a (very brief) overview of the DSpace 2013 RoadMap.

In order to make this information more widely available, I've recorded a 
video screencast (27 mins) of this OR13 talk and made it available at:
http://youtu.be/JtnjPk9qS_k

The slides presented are also freely available at:
http://www.slideshare.net/tdonohue/dspace-roadmap-vision-2013-or13

The drafted 3-5 year vision statement is on our wiki at:
https://wiki.duraspace.org/display/DSPACE/DSpace+2013+Vision+Document

== Your Feedback on 3-5 Year Vision ==

I'd encourage everyone to review the draft 3-5 year vision for DSpace 
software. This vision was brainstormed by a small group of DSpace 
institutions as an initial step towards finding ways to enhance DSpace 
to meet the ever-changing needs of a modern institutional repository 
platform. DuraSpace was involved in organizing these discussions, but 
the vision itself was created by your colleagues in the DSpace community.

We want your feedback! This vision is by no means complete or 
finalized, and we encourage you and your colleagues to let us know what 
you think. We've created a wiki page to capture comments/feedback on 
this vision, along with any use cases / needs you feel are important 
ones that DSpace should strive to meet:

https://wiki.duraspace.org/display/DSPACE/DSpace+2013+Vision+Document

(Feel free to add your own comments to the bottom of that page)

Once we have a vetted listing of DSpace use cases / needs, our informal 
Vision Team will be working with Committers  other technology folks 
to create a possible implementation plan / technical roadmap. We also 
anticipate establishing a community-led (and likely 
community-funded/supported) implementation project in order to make the 
final vision a reality. Much of this process is still yet to be decided, 
but will be made transparent as the initiative moves forward.

== Help Out! Take a More Active Role! ==

Each of you has an opportunity to take as active a role as you desire 
through this 3-5 year vision and subsequent community implementation 
project. At a minimum, we hope that you will provide feedback on the 
vision and use cases which are important to you and your institution.

However, if you'd like to take a more active role, we welcome anyone to 
join our informal Vision Team. This Vision Team is essentially 
self-organized at this time, but we welcome anyone who is interested in 
being involved. If you or your institution would like to become more 
directly involved in these vision discussions, please get in touch with 
myself (tdono...@duraspace.org) or Jonathan Markow (jjmar...@duraspace.org).

For those wanting to take a more active role, we also have created a 
public 'dspace-vision' list for detailed vision discussions at:
https://groups.google.com/forum/#!forum/dspace-vision

Although that 'dspace-vision' list is mostly for organizing thoughts and 
occasional Vision Team meetings, you are welcome to join that list to 
listen in or take a more active role (the list archives are also 
publicly browseable/searchable). Any major announcements or additional 
calls for community feedback/support will be posted to the 
'dspace-general' mailing list as well.

--

There will be much more information about this DSpace 3-5 Year Vision 
initiative in the coming months. As mentioned, we want to make this 
community initiative as transparent as possible, in order to ensure we 
get feedback from as many of you as possible.

If you have any questions, comments or concerns, please do feel free to 
respond to this thread, or email myself (tdono...@duraspace.org) or 
Jonathan Markow (jjmar...@duraspace.org).

I'm excited to see this initiative move forward  hear your feedback and 
ideas as we do so. Let's build a better DSpace, together.

Tim Donohue
Technical Lead for DSpace
DuraSpace.org

--
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] Announcing DSpace 3.2 Release : provides bug and security fixes to 3.x platform

2013-07-25 Thread Tim Donohue
DSpace Community,

Today we are proud to announce DSpace 3.2, a new bug-fix / security-fix 
release for the 3.x platform.

DSpace 3.2 addresses a number of issues that were found to affect 3.0 or 
3.1. These fixes include:

* Several bug fixes to the OAI-PMH interface
* Resolved memory leak in JSPUI
* Resolved security issue in JSPUI
* Several minor configuration / build fixes
* Other minor fixes

A detailed list of resolved issues can be found at:
https://wiki.duraspace.org/display/DSPACE/DSpace+Release+3.2+Notes

We recommend that all 3.x JSPUI users upgrade to 3.2 in order to resolve 
a memory leak and fix a potential security vulnerability.
Any 3.x OAI-PMH users are also encouraged to upgrade, as several 
recently reported OAI-PMH issues have now been resolved.

3.2 Installation and Upgrade instructions:
* Installation: https://wiki.duraspace.org/display/DSDOC3x/Installation
* Upgrade from 3.x to 3.2: 
https://wiki.duraspace.org/display/DSDOC3x/Upgrading+From+3.0+to+3.x
* Upgrade (general instructions): 
https://wiki.duraspace.org/display/DSDOC3x/Upgrading+a+DSpace+Installation

DSpace would not exist without the hard work and support of the 
community! We'd like to thank each of you for continuing to use DSpace, 
support DSpace, test DSpace, and provide feedback to the developers.

Sincerely,

Tim Donohue, on behalf of the DSpace Committers

--
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] Announcing DSpace 1.8.3 Release: provides a JSPUI security patch to 1.8.x platform

2013-07-25 Thread Tim Donohue
DSpace Community,

Today we'd like to also announce DSpace 1.8.3, a security release for 
the 1.8.x platform.

DSpace 1.8.3 addresses a security vulnerability in the JSPUI. Although 
there are no known exploits of this vulnerability, we recommend all 
1.8.x JSPUI users upgrade to 1.8.3 or 3.2. This JSPUI security fix has 
been backported to 1.8.3 (from 3.2) as per our current DSpace Software 
Support Policy [1].

This 1.8.3 release also contains minor improvements that make 1.8.x more 
Git/GitHub friendly, allowing users to more easily work with 1.8 in 
Git/GitHub.

More details on the 1.8.3 release (including download links) can be 
found at:
https://wiki.duraspace.org/display/DSPACE/DSpace+Release+1.8.3+Notes

Recommendations:
* We highly recommend that all 1.8.x JSPUI users either upgrade to 1.8.3 
or 3.2 to fix the JSPUI security vulnerability.
* If you are unable to upgrade at this time, a manual patch has been 
provided at https://jira.duraspace.org/browse/DS-1603 (you must register 
to access this ticket)

1.8.3 Installation and Upgrade instructions:
* Installation: https://wiki.duraspace.org/display/DSDOC18/Installation
* Upgrade from 1.8.x to 1.8.3: 
https://wiki.duraspace.org/display/DSDOC18/Upgrading+From+1.8+to+1.8.x
* Upgrade from 1.8.x to 3.2: 
https://wiki.duraspace.org/display/DSDOC3x/Upgrading+From+1.8.x+to+3.x
* Upgrade (general instructions): 
https://wiki.duraspace.org/display/DSDOC18/Upgrading+a+DSpace+Installation

DSpace would not exist without the hard work and support of the 
community! We'd like to thank each of you for continuing to use DSpace, 
support DSpace, test DSpace, and provide feedback to the developers.

Sincerely,

Tim Donohue, on behalf of the DSpace Committers

[1] DSpace Software Support Policy: 
https://wiki.duraspace.org/display/DSPACE/DSpace+Software+Support+Policy

--
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] Announcing DSpace 1.7.3 Release: provides a JSPUI security patch to 1.7.x platform

2013-07-25 Thread Tim Donohue
DSpace Community,

Today we'd like to also announce DSpace 1.7.3, a security release for 
the 1.7.x platform.

DSpace 1.7.3 addresses a security vulnerability in the JSPUI. Although 
there are no known exploits of this vulnerability, we recommend all 
1.7.x JSPUI users upgrade to 1.7.3 (or 1.8.3 or 3.2). This JSPUI 
security fix has been backported to 1.7.3 (from 3.2) as per our current 
DSpace Software Support Policy [1].

This 1.7.3 release also contains minor improvements that make 1.7.x more 
Git/GitHub friendly, allowing users to more easily work with 1.7 in 
Git/GitHub.

More details on the 1.7.3 release (including download links) can be 
found at:
https://wiki.duraspace.org/display/DSPACE/DSpace+Release+1.7.3+Notes

Recommendations:
* We highly recommend that all 1.7.x JSPUI users either upgrade to 1.7.3 
or 1.8.3 or 3.2 to fix the JSPUI security vulnerability.
* Users of previous versions of DSpace (1.6.x or below), who depend on 
the JSPUI, are also encouraged to upgrade to 1.7.3 or 1.8.3 or 3.2 to 
fix this vulnerability.
* If you are unable to upgrade at this time, a manual patch has been 
provided at https://jira.duraspace.org/browse/DS-1603 (you must register 
to access this ticket)

1.7.3 Installation and Upgrade instructions:
* Installation: https://wiki.duraspace.org/display/DSDOC17/Installation
* Upgrade from 1.7.x to 1.7.3: 
https://wiki.duraspace.org/display/DSDOC18/Upgrading+From+1.7+to+1.7.x
* Upgrade from 1.7.x to 1.8.3: 
https://wiki.duraspace.org/display/DSDOC18/Upgrading+From+1.7.x+to+1.8.x
* Upgrade (general instructions): 
https://wiki.duraspace.org/display/DSDOC18/Upgrading+a+DSpace+Installation

DSpace would not exist without the hard work and support of the 
community! We'd like to thank each of you for continuing to use DSpace, 
support DSpace, test DSpace, and provide feedback to the developers.

Sincerely,

Tim Donohue, on behalf of the DSpace Committers

[1] DSpace Software Support Policy: 
https://wiki.duraspace.org/display/DSPACE/DSpace+Software+Support+Policy

--
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] Request for information on repository request-copy Button

2013-10-18 Thread Tim Donohue
Hi All,

It looks like the delay on this Request a Copy feature is that we 
currently don't have a (mergeable) GitHub Pull Request to review  
accept into the DSpace codebase.

As Emilio noted, there are three (interlinked) tickets open:
https://jira.duraspace.org/browse/DS-830
https://jira.duraspace.org/browse/DS-1585
https://jira.duraspace.org/browse/DS-824

However, as of today, we only have a single Pull Request (created by 
Emilio for the XMLUI version only), and unfortunately it is currently in 
an unmergeable state (it has code conflicts which need resolving, see 
the comments):

https://github.com/DSpace/DSpace/pull/260

Per our DSpace Code Contribution Guidelines, the DSpace Committers 
highly recommend submitting new features as a GitHub Pull Request:

https://wiki.duraspace.org/display/DSPACE/Code+Contribution+Guidelines

To try and clarify even further:
* Submitting code contributions via a GitHub Pull Request means that it 
will be reviewed more quickly and is much more likely to be accepted as 
part of the next release of DSpace.
* Without a Pull Request, the code review is more likely to be delayed, 
as the Committers will need to locate a volunteer to steward your code 
and create the Pull Request on your behalf.

This all being said, it sounds like the DSpace 4.0 Release Team (in 
conjunction with the Committers) is making an effort to see if this 
Request a Copy feature can still be added into the upcoming DSpace 4.0 
release (even though our advertised Pull Request deadline for 4.0 was 
back on Oct 7). There's no guarantee it'll make it into 4.0, but we'll 
see what we can reasonably do.

I hope this helps to clarify the status of these tickets. I think the 
Committers would love to see this feature in DSpace. But the reality 
seems to be that we haven't found the volunteer(s) to generate the Pull 
Request(s) that are needed to kickstart the process. (Emilio is already 
chipping in, and we thank him for that, but we just need to get his PR 
fixed so it can be merged.)

If there are further questions, please feel free to ask. We'd be glad to 
explain further as needed.

- Tim

-- 
Tim Donohue
Technical Lead for DSpace  DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org

On 10/17/2013 12:25 PM, emilio lorenzo wrote:
 Just some remarks:


 There are three JIRA issues, differents UI and (I think) differents
 functionalities
 https://jira.duraspace.org/browse/DS-830 Request a Copy Addon :
 Requesting access to restricted items in DSpace   (JSPUI)
 https://jira.duraspace.org/browse/DS-1585   Request a Copy Addon :
 Requesting access to restricted items in DSpace (XMLUI version)
 https://jira.duraspace.org/browse/DS-824Request Copy function for
 XMLUI; would allow author of item to give viewing privs to restricted item

 And, according JIRA system...
 there is a JSPUI version  developed by University of Minho
 There is a  XMLUI version , written by our company, under a contract of
 the Spanish Oceanographic Institute. This code can be considered a
 direct translation to XMLUI  of UMinho functionality, and as such is
 declared in the credits. The code is available in
 https://github.com/muelle/DSpace/commit/0eb9ca3b055b2f34fbe9aabd6458fe4cd45e4ad5
 (referenced in the jira ticket)


 The xmlui code is in use (at least)  in Spanish Oceanographic Institute,
 perhaps in SEAFDEC/AQD  (Elvi Nemiz could update on this)  and in a
 couple of Spanish Universities. One of these have asked us for further
 development.

 Best regards

 Emilio Lorenzo




 El 17/10/2013 16:33, Stevan Harnad escribió:
 Dear Eloy, Bram  Carol,

 As Eloy was the first to adopt the Button for DSpace, could you or
 Bram (or anyone else) please help with this?

 It apparently needs an upgrade, and it's especially important to
 provide and embed it in DSpace core at this crucial time in the
 evolution of OA policy worldwide.

 The Button is an essential component in an effective OA mandate.

 http://dspace.2283337.n4.nabble.com/Re-Use-of-e-print-request-button-td4665355.html
 https://wiki.duraspace.org/display/DSPACE/RequestCopy

 Many thanks for any help or information you can provide,

 Stevan

 Begin forwarded message:

 - Original Message -
 From: Hutchinson, Alvin hutchins...@si.edu
 mailto:hutchins...@si.edu
 To: hbosc-tcher...@orange.fr mailto:hbosc-tcher...@orange.fr
 Sent: Thursday, October 17, 2013 3:28 PM
 Subject: Request for information on repository request-copy Button

 I received a message stating that you are interested in the use of
 Request Copy button in repositories.

 We at the Smithsonian Libraries use DSpace and have employed the
 Request Copy button for several years.

 However, it is becoming problematic as the plugin does not seem to
 have any active development or upgrades.

 I'm not sure how familiar you are with DSpace but for several
 versions, there has been an XML user interface as well as the
 original JSP (java server pages) interface.


 The Request Copy plugin only works

Re: [Dspace-general] OSTP, FASTR, PAPS: Request-Copy Button will be native to both DSpace EPrints December

2013-10-29 Thread Tim Donohue

  
  

To clarify, 

The "Request for Copy" feature was added to the DSpace 4 codebase by
Andrea Bollini and Ivan Masr, who both volunteered their time
to prepare the old code for 4.0. Andrea and Ivan reworked and
updated the "Request for Copy" code originally written by U of Minho
and AdnRomnRuiz at Arvo Consultores. They had additional support
from other DSpace Committers in this process, namely Hardy Pottinger
(who helped with Oracle support).

Not taking anything away from Bram here, he and others on our DSpace
Committer team helped advocate for its quick inclusion into the
upcoming 4.0 release. But, I did want to be sure that Andrea and
Ivan received the recognition for their hard work in making sure
this feature makes it into 4.0 in December.

    Thanks,

Tim Donohue

Technical Lead for DSpace  DSpaceDirect

DuraSpace.org | DSpace.org | DSpaceDirect.org

On 10/28/2013 10:54 AM, Stevan Harnad
  wrote:


  



  --
Forwarded message --
From: Bram Luyten b...@mire.be
Date: Mon, Oct 28, 2013 at 10:39 AM
Subject: Re: Request for information on repository
request-copy Button
the "pull request" (code contribution) has
been merged, meaning that the Request for Copy feature will
be part of DSpace 4, both for XMLUI and JSPUI.
It is possible that some additional tweaks and entries in
the documentation will be added over the next few weeks,
ramping up to the expected release of DSpace 4 in December.
https://jira.duraspace.org/browse/DS-824
Thanks to everyone who has advocated for and contributed to
this feature, it has been long overdue.
  
  

  

  

  

  
  
  
Bram
Luyten @mire
  2888
  Loker Avenue East, Suite 315,
  Carlsbad, CA. 92010
  Esperantolaan
  4, Heverlee 3001, Belgium
2888
Loker Avenue East, Suite 315,
Carlsbad, CA. 92010
  Esperantolaan
4, Heverlee 3001, Belgium
  www.atmire.com
  

  

  
  
  Many thanks to Bram Luyton for making the Request Copy
  native to DSpace as of December.
  
  
  Please, those with influence over the
implementation of the forthcoming OSTP OA Directive
and the proposed FASTR and PAPS OA Mandates, inform
the policy makers about the critical importance of
making sure that the deposit requirement should be
immediate (not just after embargoes have elapsed),
that the deposit should be done by the fundee (and
not the publisher!), and that the deposit should be
in the fundee's institutional repository (not
institution external: the deposit can then be
exported automatically to whatever
institution-external repositories desired).
  
  
  The Button is one of the reasons immediate
institutional deposit is so important:
  
  
  1.not only does immediate institutional
deposit ensure that everything is deposited, at a
specified, verifiable and natural date (the date of
the acceptance letter)
  
  
  2.not only does it recruit the
institution in monitoring and ensuring that the
funding condition is fulfilled
  
  
  3.not only does it ensure that only one
deposit ever needs to be done -- and is done by the
party bound by the funding conditions (the fundee)
and not a 3rd party whose interests are in conflict
with it (the publisher)
  

[Dspace-general] Fwd: DSpace 4.0 Testathon begins Nov 4 -- Users / Feedback wanted

2013-11-01 Thread Tim Donohue

  
  

 Original Message
  
  

  
Subject:

[Dspace-tech] DSpace 4.0 Testathon begins Nov 4 -- Users
  / Feedback wanted
  
  
Date: 
Tue, 29 Oct 2013 17:03:46 -0400
  
  
From: 
Mark H. Wood mw...@iupui.edu
  
  
To: 
dspace-t...@lists.sourceforge.net
  

  
  
  
  The first Release Candidate for DSpace 4.0 will soon be available for
testing.  Some new features that might interest you include:

  - A new look and feel for JSPUI, with several other improvements
  - A number of features of XMLUI have been ported to JSPUI
  - A REST API exposing repository objects
  - Support for automatically creating DOIs during ingestion.

There's much more.  Please see the Release Notes at:

  https://wiki.duraspace.org/display/DSPACE/DSpace+Release+4.0+Notes

ATTENTION ORACLE SITES:

Hi, sorry to shout at you, but now that we have your attention, please
do plan on testing the release candidates of DSpace 4.0 on your own
infrastructure. We'd like to minimize the surprises on the day that
4.0 is officially released, and the best way to do that is with your
help. If at all possible, please consider testing DSpace 4.0, to
ensure it is compatible with Oracle. Ideally, this would mean testing
a new install, and an upgrade. Thanks!

INVITATION TO TRANSLATORS:

If you are willing to translate DSpace message catalogs into another
language:  the 4.0 catalogs should be nearly stable now.

TESTATHON and NEXT STEPS:

We plan to tag RC1 on 31-Oct-2013.  There will be another
announcement when it is ready for download.  If you would like to try
out the next release of DSpace in your own test environment, please
do, and tell us what you find.

The following Monday, 04-Nov-2013, begins the 4.0 Testathon, which
continues through the 15th.  RC1 will be available on
http://demo.dspace.org.  You can try it out without installing your
own instance, and your feedback would be appreciated.  Look for the
red Feedback button to report issues with the demo. site.

The actual use of a software product is always more varied and
surprising than the developers and maintainers imagined.  Please help
us ensure that DSpace 4.0 will do what you expect.

-- 
Mark H. Wood, DSpace 4.0 Release Coordinator


  
  -- 
Tim Donohue
Technical Lead for DSpace  DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org
  


  



signature.asc
Description: PGP signature
--
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951iu=/4140/ostg.clktrk
___
DSpace-tech mailing list
dspace-t...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
--
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951iu=/4140/ostg.clktrk___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] Welcome to the latest DSpace committer: (Luigi) Andrea Pascarelli

2013-11-14 Thread Tim Donohue
Dear DSpace Community,

The DSpace committers team are delighted to announce a new member to the
group: (Luigi) Andrea Pascarelli from CINECA (http://www.cineca.it/).
Please join us in welcoming Andrea!

Andrea is a Java Developer, with six years of experience in the field.
His experience is primarily in web application development. At CINECA,
he works on integration, development and maintenance of large
systems for digital library and electronic publishing, including DSpace.
Andrea is a certified Programmer for Java 6 (SCJP) and received his
Bachelor's degree in Computer Engineering in December 2006. In addition,
Andrea is the lead developer on the DSpace-CRIS project:

http://cilea.github.io/dspace-cris/

You can read even more about Andrea on his LinkedIn profile at:

http://www.linkedin.com/in/luigiandreapascarelli

We are always on the lookout for new developers, contributors, and
committers within the DSpace community. Anyone who would like to get
more involved is encouraged to do so. You are also welcome to contact us
at any time if you'd like some ideas of how to start contributing:

https://wiki.duraspace.org/display/DSPACE/DSpaceContributors

Contributions can take many forms, from writing code to editing
documentation, or testing new releases to designing new themes for our
user interfaces.

If you or someone you know has been an active DSpace contributor for
some time, you can also nominate that person to become our next
committer! Nomination details are available at:

https://wiki.duraspace.org/display/DSPACE/Committer+Nominations

Thanks,

The DSpace Committers Group

--
DreamFactory - Open Source REST  JSON Services for HTML5  Native Apps
OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
Free app hosting. Or install the open source package on any LAMP server.
Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
http://pubads.g.doubleclick.net/gampad/clk?id=63469471iu=/4140/ostg.clktrk
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] DuraCloud - Automatic or Scheduled Backup?

2013-12-04 Thread Tim Donohue


On 12/4/2013 8:02 AM, Mark H. Wood wrote:
 On Tue, Dec 03, 2013 at 03:45:31PM -0600, Martin Courtois wrote:
 I'd be interested to hear from current DuraCloud users on how you're
 scheduling backups.  Are you using the Automatic Sync Changes feature to
 backup changes as they happen, or are you running an entire backup on a
 regular basis?  Maybe a combination of the two?

 We're doing daily differential backups:  a cron job exports AIPs for
 any objects that have changed since the last successful backup, and
 then sync.s those up to DuraCloud in a single pass.  The script writes
 a timestamp file if nothing went wrong, and uses it (plus a little
 overlap added) as the starting point for the next run.

A slight tangent here, for folks who may not be aware of it. The 
Replication Task Suite is a great route towards scheduling these 
automatic incremental AIP backups via cron (on whatever schedule you 
feel necessary). The Replication Task Suite can be used with DuraCloud 
or just with a normal onsite backup (e.g. backup to a mounted drive, or 
similar).

The Replication Task Suite is still a separate addon, but we've tried to 
make it simple to install into an existing DSpace:
https://wiki.duraspace.org/display/DSPACE/ReplicationTaskSuite

Once installed, you can use the functionality to Automatically Sync 
Changes (via a Queue). This automated sync can be processed on whatever 
schedule you want -- and it does exactly what Mark describes above. Any 
changes that occur in DSpace are written to the sync queue. Then when 
you next process the queue (via cron), those AIPs will be regenerated 
and resynced with your backup location.

https://wiki.duraspace.org/display/DSPACE/ReplicationTaskSuite#ReplicationTaskSuite-AutomaticallySyncChanges%28viaQueue%29

There's even an example cron command to process the queue in the 
documentation above -- see the section on Processing the Sync Consumer 
Queue.

So, this doesn't answer the question of how frequently you should 
perform these AIP backups, but rather a recommended route to do so 
(whether you are using DuraCloud or not).

- Tim


--
Sponsored by Intel(R) XDK 
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631iu=/4140/ostg.clktrk
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] [Dspace-devel] DSpace 4.0 released!

2013-12-17 Thread Tim Donohue
Hello DSpace Commmunity,

One additional enhancement which we realized we accidentally left off 
the (long) list of 4.0 features/improvements:

* Several improvements which help Google Scholar (and other search 
engines) to better index your DSpace content and make it more findable. 
These improvements were requested by the Google Scholar team.

More information on these specific Google Scholar improvements is now 
available in the 4.0 Release Notes (look for the Google Scholar logo):
https://wiki.duraspace.org/display/DSDOC4x/Release+Notes

Congrats to everyone on this major release! It is amazing how many new 
features, improvements and bug fixes were included. We have our highly 
active community to thank, as well as our dedicated Committer team!

- Tim

On 12/17/2013 8:47 AM, Mark H. Wood wrote:
 Dear DSpace Community:

 On behalf of the DSpace developers, I would like to formally announce
 that DSpace 4.0 is now available!

 DSpace 4.0 can be downloaded immediately at either of the following
 locations:

 * SourceForge: https://sourceforge.net/projects/dspace/files/
 * GitHub: https://github.com/DSpace/DSpace/  (see the dspace-4.0 tag)

 In addition, you are welcome to try out DSpace 4.0 on
 http://demo.dspace.org/ and continue to provide any early feedback you
 may have.

 == New Features and Improvements in 4.0 ==

 General:

 *  **new** REST API module based on JAX RS 1.0;
 *  **new** Request a Copy for files that are not yet available for
 public downloading;
 *  **new** DOI Support;
 *  Discovery formally replaces legacy Search  Browse;
 *  SWORDv2 module update;
 *  Improved command line features;
 *  Support simple embargo in AIP import/export;
 *  Support running handle server and application container on separate
 machines;
 *  Improvements to LDAP Authentication;
 *  Media filter generates better-looking thumbnails;
 *  Curation Task for Consuming Web Services;

 JSPUI Specific:

 * **new** A new Bootstrap-based default look and feel
 * **new** Integrated PubMed, Arxiv and CrossRef metadata lookup

 XMLUI Specific:

 *  Support simple embargo in item display;
 *  Language switch;
 *  Mobile Theme matures from beta;

 For much more information on each of these features, please visit our
 4.0 Release Notes:

https://wiki.duraspace.org/display/DSDOC4x/Release+Notes

 == 4.0 Documentation ==

 The DSpace 4.0 documentation is available online at:
 https://wiki.duraspace.org/display/DSDOC4x/

 A PDF copy of the documentation is still distributed with the
 software.   In addition, it can also be downloaded from:
 http://www.dspace.org/latest-release/

 == 4.0 Acknowledgments ==

 The DSpace application would not exist without the hard work and
 support of the community. Thank you to the many developers who have
 worked very hard to deliver all the new features and
 improvements. Also thanks to the users who provided input and feedback
 on the development, as well those who participated in the
 testathons. Additionally I would like to thank Tim Donohue of
 DuraSpace for ensuring that DSpace 4.0 went off without a hitch.

 A detailed listing of all known people/institutions who contributed
 directly to DSpace 4.0 is available in the Release Notes.  If you
 contributed and were accidentally not listed, please let us know so
 that we can correct it!

 For DSpace 4.0, we had a total of 59 individuals contribute code, bug
 reports, and bug fixes.  A big thanks goes out to everyone who
 participated.  We hope you'll continue to be a valuable addition to
 the DSpace community for the next release and beyond!

 == More Information ==

 More information on this release is also available in the DSpace 4.0
 Release Notes at:

https://wiki.duraspace.org/display/DSDOC4x/Release+Notes

 As always, we are happy to hear back from the community about DSpace.
 Please let us know what you think of 4.0!

 - Mark Wood, on behalf of the DSpace 4.0 Release Team, and all the
DSpace developers.



 --
 Rapidly troubleshoot problems before they affect your business. Most IT
 organizations don't have a clear picture of how application performance
 affects their revenue. With AppDynamics, you get 100% visibility into your
 Java,.NET,  PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
 http://pubads.g.doubleclick.net/gampad/clk?id=84349831iu=/4140/ostg.clktrk



 ___
 Dspace-devel mailing list
 dspace-de...@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-devel


--
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET,  PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http

Re: [Dspace-general] DSpace 4.0 upgrade failure

2013-12-17 Thread Tim Donohue
Hi Alain,

It looks like we have a typo in our Upgrade instructions.  Apologies.

When upgrading, the mvn -U clean package command MUST be run from the 
[dspace-source] directory (NOT from [dspace-source]/dspace/).

Running the command from [dspace-source] ensures that *all* DSpace 
modules are recompiled/rebuilt for DSpace 4.0. (Whereas, running the 
build from [dspace-source]/dspace/ performs a quick build, which does 
NOT recompile all modules.)

I've corrected the upgrade documentation at:
https://wiki.duraspace.org/display/DSDOC4x/Upgrading+From+3.x+to+4.0

Feel free to email us again on this list if you encounter any other issues.

- Tim

On 12/17/2013 12:47 PM, Alain Tschanz wrote:
 Hello,

 I’m trying to upgrade from DSpace 3.2 to 4.0, but I get the following error:

 [INFO]
 

 [INFO] Reactor Summary:

 [INFO]

 [INFO] DSpace Addon Modules .. SUCCESS [2.002s]

 [INFO] DSpace Kernel :: Additions and Local Customizations  SUCCESS [7.016s]

 [INFO] DSpace XML-UI (Manakin) :: Local Customizations ... FAILURE [1.897s]

 [INFO] DSpace LNI :: Local Customizations  SKIPPED

 [INFO] DSpace JSP-UI :: Local Customizations . SKIPPED

 [INFO] DSpace REST (JAX RS 1 - Jersey) :: Local Customizations  SKIPPED

 [INFO] DSpace SWORD :: Local Customizations .. SKIPPED

 [INFO] DSpace SWORD v2 :: Local Customizations ... SKIPPED

 [INFO] DSpace SOLR :: Local Customizations ... SKIPPED

 [INFO] DSpace OAI 2.0 :: Local Customizations  SKIPPED

 [INFO] DSpace Assembly and Configuration . SKIPPED

 [INFO]
 

 [INFO] BUILD FAILURE

 [INFO]
 

 [INFO] Total time: 12.123s

 [INFO] Finished at: Tue Dec 17 13:40:46 EST 2013

 [INFO] Final Memory: 29M/69M

 [INFO]
 

 [ERROR] Failed to execute goal
 org.apache.maven.plugins:maven-resources-plugin:2.5:resources
 (default-resources) on project xmlui: Error loading property file
 '/home/webmaster/Downloads/DSpace-dspace-4.0/dspace/modules/xmlui/../../../target/build.properties'
 - [Help 1]

 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
 execute goal
 org.apache.maven.plugins:maven-resources-plugin:2.5:resources
 (default-resources) on project xmlui: Error loading property file
 '/home/webmaster/Downloads/DSpace-dspace-4.0/dspace/modules/xmlui/../../../target/build.properties'

   at
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)

   at
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)

   at
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)

   at
 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)

   at
 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)

   at
 org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)

   at
 org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)

   at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)

   at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)

   at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)

   at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)

   at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)

   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

   at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

   at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

   at java.lang.reflect.Method.invoke(Method.java:601)

   at
 org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)

   at
 org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)

   at
 org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)

   at
 org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)

 Caused by: org.apache.maven.plugin.MojoExecutionException: Error loading
 property file
 '/home/webmaster/Downloads/DSpace-dspace-4.0/dspace/modules/xmlui/../../../target/build.properties'

   at
 org.apache.maven.plugin.resources.ResourcesMojo.execute(ResourcesMojo.java:316)

   at
 org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)

   at
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)

   ... 19 more

 Caused by: org.apache.maven.shared.filtering.MavenFilteringException:
 

Re: [Dspace-general] Search in DSpace

2014-02-14 Thread Tim Donohue
Hi All,

Just to add to the discussion here... these are all great questions and 
worth considering. If there are issues with how Discovery/Solr works or 
if it's not ideal, then we have options to either fix it or look towards 
a better solution altogether.

Apologies for what is a rather long email, but I'm trying to best 
explain the Committer thought processes here...

First, it's worth being aware that Discovery/Solr is actually being used 
both for Search and for Browse. Prior to Discover/Solr, Search was 
performed via Lucene, while Browse was a custom built system which used 
the underlying database (Postgres).

To try to explain the Committer point of view/discussions that have 
taken place since then:
* Committers began to run into limitations of our custom browse system 
and Lucene based on some of the Search/Browse feature requests coming 
in. While some of these features could have been implemented in Lucene, 
we noticed that a combined Search/Browse in Solr was beginning to look 
more favorable.
* Committers have been struggling with the sometimes patchwork nature 
of the DSpace codebase (which happens after 10 years). DSpace is 
extremely powerful and extremely configurable. But, as we have limited 
resources, we've come to the realization that we need to simplify and 
modularize the codebase little by little (while trying to ensure DSpace 
retains its strong niche).
* Committers were also noticing that more and more open source systems 
these days (Hydra, Islandora, even EPrints) are using Solr to handle 
both Search  Browse. Solr has begun to become a defacto standard in 
many ways, and it's used well beyond the IR community as well.

However, even within the Committers group, not all have agreed that Solr 
is *the best solution*, which is part of the reason why Discovery 
exists. Without getting too technical, Discovery is essentially a 
generic search/browse layer built for DSpace. Discovery itself 
actually could/can provide multiple plugins for multiple search engines. 
The Committers have actually discussed building a Lucene plugin for 
Discovery and even an Elastic Search plugin for Discovery.

So, in the future, it's possible DSpace Search/Browse could look like 
this (and individual institutions could choose which plugin you wanted):

* Discovery Search/Browse
 * Solr plugin for Discovery
 * Lucene plugin for Discovery (doesn't yet exist)
 * Elastic Search plugin for Discovery (doesn't yet exist)

So, the Committers have never decided to completely remove Lucene 
support forever. All that we've decided is that we need to standardize 
on a common Search/Browse platform (which is Discovery), because we just 
don't have enough development resources right now to build/maintain 
multiple completely separate search/browse codebases (Discovery  
traditional Lucene search are entirely separate codebases, and those 
separate codebases still exist even in DSpace 4.x). The reality though 
is that currently Discovery only supports Solr. We hope that it can 
support Lucene and other search tools as well, but we need to find 
committer resources or other volunteers to help us build those 
additional search plugins.

I also fully agree here that it'd be wonderful to find better ways to 
survey our actual end users to better determine their search/browse 
needs out of DSpace. This is something that I'd also love to see happen. 
Unfortunately it's not a role the Committers are able to play as we are 
not experts in writing/drafting/promoting user surveys. Perhaps however 
the upcoming DSpace Steering Committee and/or DCAT could help us in 
finding ways to survey the community and our users.

This does sound like a discussion we could begin at the upcoming 
DuraSpace Sponsors Summit in March (for those in attendance). In general 
we don't always have a smooth process in place to survey the community 
about these decisions. The Committers team sometimes has less than 
perfect information and we sometimes have to make difficult decisions 
based on our existing resources (and it's not always clear which 
decisions are potentially controversial to others in the community). So, 
this is a great discussion to be starting, both specifically with 
regards to Search/Browse, and generally with regards to how best to 
survey our widespread community, etc.

I hope this helps the discussion. Glad to also clarify anything I've 
said if it's unclear.

- Tim


On 2/13/2014 8:15 PM, Jeffrey A Trimble wrote:
 On a completely end user note, we have found our Discovery service for our
 Library is not well liked by undergraduate students.  The results are too
 large most of the time (10K+) and they (the user) frustrate easily if they
 have to learn to customize the search.

 Our Information Literacy/Bibliographic Instruction Librarians have stopped
 teaching Discovery Layer Services and the norm.  (We us EBSCO Discovery
 Service which is a Rolls Royce!).  The EDS for us not only searches our
 local loads 

Re: [Dspace-general] multiple domains on single instance

2014-06-16 Thread Tim Donohue
Hi,

The easiest way to support multiple domains is to install several DSpace 
instances (separate repository per URL) behind a single Apache webserver.

As a basic example, you could do the following:

1) Install a DSpace for Institution1, with Tomcat running on port 8080

2) Install a separate DSpace for Institution2, with Tomcat running on 
port 8081 (i.e. a different port)

3) Install an Apache web server. Configure it to respond to multiple 
URLs via different VirtualHosts...e.g. see: 
https://httpd.apache.org/docs/2.2/vhosts/examples.html

4) Configure Apache to forward requests for 
http://institution1.com/repo; to the Tomcat on port 8080, using 
something like mod_proxy: 
https://httpd.apache.org/docs/2.2/mod/mod_proxy.html

5) Configure Apache to forward requests for 
http://institution2.com/repo; to the Tomcat on port 8081, again using 
something like mod_proxy.

Here's a full sample of configuring Apache using mod_proxy + a 
VirtualHost to forward to a Tomcat: http://stackoverflow.com/a/962928

By the way, just an FYI. It's usually best to send this type of 
technical question to our dspace-tech mailing list, as that's our 
primary tech support list: 
https://lists.sourceforge.net/lists/listinfo/dspace-tech

- Tim

On 6/16/2014 9:05 AM, Ozren Lapcevic wrote:
 Hi,

 does Dspace support multiple domains (sites or institutions) on single
 instance?

 We have to support multiple institutions. Each institution should have
 separated repository accessible via unique URL, e.g.
 Institution1 - http://institution1.com/repo
 Institution2 - http://institution2.com/repo

 Is this possible with Dspace? Where can I look for more info?

 Best regards,


--
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing  Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] DSpace Sessions/Slides from OR14

2014-06-24 Thread Tim Donohue
Hi all,

For anyone who was unable to attend Open Repositories 2014 (or just 
wants to review what they saw), I've begun a wiki page which provides 
links to the slides of a few of the DSpace-related sessions at the 
conference:

https://wiki.duraspace.org/display/DSPACE/OR2014+DSpace+Sessions

Currently, this page is mostly from DuraSpace related talks. Once all 
OR14 slides are posted, I'll make sure to update this page with the 
links. In the meantime, you are more than welcome to add links to any 
other OR14 slides you are aware of.

Thanks,

Tim

-- 
Tim Donohue
Technical Lead for DSpace  DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org

--
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] Job opening at DuraSpace: Devops Engineer / Systems Administrator

2014-06-30 Thread Tim Donohue
DuraSpace, a not-for-profit serving the needs of hundreds of academic 
and cultural heritage institutions worldwide, is seeking an experienced 
operations specialist to manage the administration and automation of 
technical infrastructure and software systems used by the DuraSpace 
organization and the teams that are creating open source systems such as 
DSpace, Fedora, VIVO, and DuraCloud.



 *What's in it for you:*

 *

   You will have the opportunity to work with cutting-edge cloud tools
   to deploy, automate, and manage production SaaS applications.

 *

   You will have the freedom to design and execute automation
   strategies using the latest configuration management tools and
   frameworks.

 *

   You will have the opportunity to be engaged with several teams and
   to manage several different types of systems.

 *

   Your work will be instrumental in ensuring that culturally relevant
   digital materials are preserved for future generations.

 *

   You will have the opportunity to work for DuraSpace, a small
   not-for-profit with a collaborative, creative, and fun culture.

 *

   You will be able to work from home.

 *

   Your working hours will be flexible depending on your needs.


 Requirements

 *

   Minimum of three years of professional experience performing systems
   administration, operations, and/or devops tasks

 *

   Proficiency and experience in Linux systems administration (Ubuntu
   or Debian preferred)

 *

   Proficiency in the analysis and debugging of systems issues

 *

   Comfortable and confident creating scripts for automation

 *

   Experience with configuration management tools and procedures
   (Puppet preferred)

 *

   Familiarity with Java web application deployment and administration
   (experience with Tomcat and Apache preferred)

 *

   Excellent verbal and written communication skills


 Bonus Points

 *

   Experience managing servers in AWS (Amazon Web Services)

 *

   Experience using Git and Github

 *

   Experience managing relational databases

 *

   Experience managing NoSQL databases

 *

   Experience with ElasticSearch, LogStash, and/or Lumberjack

 *

   Experience managing Atlassian software

 *

   Comfortable with network configuration

 *

   Familiarity with agile development methods

 *

   Experience working with remote teams



 About DuraSpace

DuraSpace (duraspace.org http://www.duraspace.org/) is a software not 
for profit 501(c)3 company.  We work with academic and cultural heritage 
institutions around the world to develop and deploy open source software 
solutions for managing and providing long term access to their digital 
cultural materials.  Our mission is to provide leadership and innovation 
for open technologies that promote durable, persistent access to digital 
content. We work with a community of vibrant open source developers from 
all over the world.  We offer a number of services to our community 
based on our open source technologies to help them advance their goals 
of making materials persistent and available to all.


DuraSpace is an equal opportunity employer. We offer health and 
retirement benefits. Salary is commensurate with experience. We are 
headquartered in the Boston MA area, however most of our employees work 
virtually and are located around the USA. We are a true believer of the 
virtual office, and use several online tools to facilitate our ability 
to work as a team irrespective of physical location.


Please send a letter of interest and cv/resume to j...@duraspace.org 
mailto:j...@duraspace.org.


See this job posting online: http://duraspace.org/duraspace_jobs

--
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] Job opening at DuraSpace: Devops Engineer / Systems Administrator

2014-06-30 Thread Tim Donohue
Resending (previous message came across with odd formatting)

-

DuraSpace, a not-for-profit serving the needs of hundreds of academic 
and cultural heritage institutions worldwide, is seeking an experienced 
operations specialist to manage the administration and automation of 
technical infrastructure and software systems used by the DuraSpace 
organization and the teams that are creating open source systems such as 
DSpace, Fedora, VIVO, and DuraCloud.

== What's in it for you: ==

* You will have the opportunity to work with cutting-edge cloud tools to 
deploy, automate, and manage production SaaS applications.
* You will have the freedom to design and execute automation strategies 
using the latest configuration management tools and frameworks.
* You will have the opportunity to be engaged with several teams and to 
manage several different types of systems.
* Your work will be instrumental in ensuring that culturally relevant 
digital materials are preserved for future generations.
* You will have the opportunity to work for DuraSpace, a small 
not-for-profit with a collaborative, creative, and fun culture.
* You will be able to work from home.
* Your working hours will be flexible depending on your needs.

== Requirements ==

* Minimum of three years of professional experience performing systems 
administration, operations, and/or devops tasks
* Proficiency and experience in Linux systems administration (Ubuntu or 
Debian preferred)
* Proficiency in the analysis and debugging of systems issues
* Comfortable and confident creating scripts for automation
* Experience with configuration management tools and procedures (Puppet 
preferred)
* Familiarity with Java web application deployment and administration 
(experience with Tomcat and Apache preferred)
* Excellent verbal and written communication skills

== Bonus Points ==

* Experience managing servers in AWS (Amazon Web Services)
* Experience using Git and Github
* Experience managing relational databases
* Experience managing NoSQL databases
* Experience with ElasticSearch, LogStash, and/or Lumberjack
* Experience managing Atlassian software
* Comfortable with network configuration
* Familiarity with agile development methods
* Experience working with remote teams

== About DuraSpace ==

DuraSpace (duraspace.org) is a software not for profit 501(c)3 company. 
  We work with academic and cultural heritage institutions around the 
world to develop and deploy open source software solutions for managing 
and providing long term access to their digital cultural materials.  Our 
mission is to provide leadership and innovation for open technologies 
that promote durable, persistent access to digital content. We work with 
a community of vibrant open source developers from all over the world. 
We offer a number of services to our community based on our open source 
technologies to help them advance their goals of making materials 
persistent and available to all.

DuraSpace is an equal opportunity employer. We offer health and 
retirement benefits. Salary is commensurate with experience. We are 
headquartered in the Boston MA area, however most of our employees work 
virtually and are located around the USA. We are a true believer of the 
virtual office, and use several online tools to facilitate our ability 
to work as a team irrespective of physical location.

Please send a letter of interest and cv/resume to j...@duraspace.org.

See this job posting online: http://duraspace.org/duraspace_jobs

--
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] Job: Digital Preservation Network (DPN) Services Manager and Technology Manager

2014-07-22 Thread Tim Donohue
On behalf of the Digital Preservation Network:

The national effort to build a Digital Preservation Network (DPN) 
continues to gain momentum as the organization, under the umbrella of 
Internet2, moves from development stage to a prototype pilot phase in 
2014. Funded by a membership that includes 60 research universities and 
foundations, DPN's objective is to preserve the academic and historical 
record by linking together existing repositories to form a sustainable, 
federated preservation network.

In line with DPN's growth, we are hiring two positions: 1) a Services 
Manager who will launch the production suite of DPN services and manage 
long-term relationships with DPN members and service providers; and 2) a 
Technology Manager who will help lead the integration of diverse 
organizations and software platforms to provide a seamless preservation 
environment for the DPN membership.

Job descriptions and instructions for applying are available here:

https://www.internet2.edu/about-us/careers/

--
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] Welcome to the latest DSpace committer: Pascal-Nicolas Becker

2014-07-29 Thread Tim Donohue
Dear DSpace Community,

The DSpace Committers team are delighted to announce a new member to the 
group: Pascal-Nicolas Becker from Technische Universität Berlin. Please 
join us in welcoming him!

Pascal is a Java Developer with eight years of repository experience. 
Starting in 2006, he worked for the Cooperated Library Network 
Berlin-Brandenburg where he was a member of the OPUS4 development team 
and hosted more than 30 repository instances. Since 2012, Pascal has 
been working for Technische Universität Berlin where he is helping to 
build an institutional repository for research data and publications 
based on DSpace. In 2014, he received his diploma in Computer Science. 
As part of his thesis on bringing repositories into the Semantic Web, he 
built an extension to add Linked (Open) Data support into DSpace 
(https://jira.duraspace.org/browse/DS-2061).

In the DSpace 4.0 release, Pascal helped build DSpace's DOI 
implementation and remote Handle Server functionality (see 4.0 Release 
Notes: https://wiki.duraspace.org/display/DSDOC4x/Release+Notes). Pascal 
has also been active on lists, contributed numerous bug fixes, and is 
planning to contribute additional features to 5.0 (e.g. an enhanced 
JSPUI file upload using HTML5, https://jira.duraspace.org/browse/DS-1994).

We are always on the lookout for new developers, contributors, and 
committers within the DSpace community. Anyone who would like to get 
more involved is encouraged to do so. You are also welcome to contact us 
at any time if you'd like some ideas of how to start contributing:

https://wiki.duraspace.org/display/DSPACE/DSpaceContributors

Contributions can take many forms, from writing code to editing 
documentation, or testing new releases to designing new themes for our 
user interfaces.

If you or someone you know has been an active DSpace contributor for 
some time, you can also nominate that person to become our next 
committer! Nomination details are available at:

https://wiki.duraspace.org/display/DSPACE/Committer+Nominations

Thanks,

The DSpace Committers Group

--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071iu=/4140/ostg.clktrk
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] [Dspace-tech] IMPORTANT NEWS: Important Info for Future Editions | Ranking Web of Repositories

2014-09-02 Thread Tim Donohue
Hi All,

Thanks for the notifications here  great analysis!

DuraSpace is tracking all these points/analysis and we've come up with a 
few additional ones (see below). I fully agree that the newly proposed 
Webometrics standards are not ideal as they will accidentally exclude a 
large portion of DSpace sites. DuraSpace will be drafting up a response 
to detail the response to these newly proposed guidelines:

http://repositories.webometrics.info/en/node/26

Some of the highest concerns have already been rightly pointed out by 
all of you:

* Rule #2 (IRs that don't use the institutional domain will be excluded) 
would cause the exclusion of some IRs which are hosted by service 
providers. As an example, some DSpaceDirect users have URLs 
https://*.dspacedirect.org which would cause their exclusion as it is a 
non-institutional domain. Other hosting providers have similar 
non-institutional domain URLs.

* Rule #4 (Repositories using ports other than 80 or 8080) would wrongly 
exclude all DSpace sites which use HTTPS (port 443).

* 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: 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 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]

* 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 
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.

Again, DuraSpace will work on a response. As you can see from my points 
above, we are already in the midst of drafting one. If I've missed any 
additional points, please do feel free to forward them my way!

- Tim

--
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] [Dspace-tech] Regarding Ranking of Repositories

2014-09-02 Thread Tim Donohue
 to upgrade to ensure they are included in the 
Rankings. (Note: we've similarly had discussions with the Google Scholar 
team to help gradually add improvements to DSpace to better meet their 
indexing needs...so it seems like the same could occur with the 
Webometrics team.)

I've copied our DuraSpace Chief Strategy Officer, Jonathan Markow, on 
this message as well.

Tim Donohue
Technical Lead for DSpace  DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org

--
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] Fwd: Open Access Repository Ranking

2014-09-11 Thread Tim Donohue
Forwarding on this announcement from the code4lib mailing list.

 Original Message 
Subject: [CODE4LIB] Open Access Repository Ranking
Date: Thu, 11 Sep 2014 17:40:12 +0200
From: Dennis Zielke zielk...@cms.hu-berlin.de
Reply-To: Code for Libraries code4...@listserv.nd.edu
To: code4...@listserv.nd.edu

*** Apologies for cross-posting! ***

Dear Colleagues,

the Open Access Repository Ranking (OARR) was launched September 9, 2014
during the Open-Access-Tage conference.[1] It is the idea and goal of
OARR to show best practices and role models of the German repository
landscape so that other repository operators can learn from them and
improve their services step by step. OARR is a research project based at
the Information Management Department of Professor Peter Schirmbacher at
the Berlin School of Library and Information Science (BSLIS),
Humboldt-Universität zu Berlin (HU Berlin) and currently lists 152 open
access publication repositories from Germany according to an open
metric. Open metric means:

- all criteria and scores are transparent;
- the metric is developed together with the open access community to
improve OARR.[2]

Most of the criteria of the metric are derived from the “2014 Census of
Open Access Repositories in Germany, Austria and Switzerland.” We
encourage all repository managers, repository software developers and
repository funders to contribute their ideas to the draft of the 2015
OARR metric using the UserVoice tool (in the “Contribute tab).[3] The
ranking is planned to be published annually at the Open-Access-Tage
conference in September. The preceding January each open access
repository that meets the OARR definition will be contacted to submit
their data via an online form.[4]

For now OARR is a ranking limited to Germany. We are planning to make it
a global ranking as soon as possible. However, this depends very much on
the feedback of professionals from as many countries as possible to make
the OARR metric a reliable and truly bottom up global benchmark for open
access repositories. It is not clear yet whether the ranking should grow
country by country or right to global scale but we are open for your ideas.

We appreciate your questions, comments and feedback.

All the best from Berlin, Germany

Dennis on behalf of the OARR team

[1] http://repositoryranking.org
[2] http://repositoryranking.org/?page_id=660
[3] http://repositoryranking.org/?page_id=660
[4] http://repositoryranking.org/?page_id=1086
https://twitter.com/OARR_org

-- 
Dennis Zielke

Humboldt-Universität zu Berlin
Arbeitsgruppe Elektronisches Publizieren
am Computer- und Medienservice (CMS)
Rudower Chaussee 26
D - 12489 Berlin

Postadresse:
Unter den Linden 6
D-10099 Berlin

Tel. +49(0)30 2093-70004

Project LAUDATIO
http://www.laudatio-repository.org/


--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] Criticality of mobile access?

2014-09-15 Thread Tim Donohue
Hi Mark,

While this doesn't necessarily answer your question, it's also worth 
considering that mobile access doesn't just mean smartphones these 
days. You also need to consider the widespread use of iPads and tablets, 
which are probably more likely to be used for DSpace/IR interaction than 
smartphones.

To this end, it's nice that we are seeing more responsive DSpace 
interfaces like the Mirage2 Theme [1] (which as you know is coming in 
DSpace 5). Such responsive interfaces adapt to the user's device, 
whether it is a computer or tablet or smartphone. (If you haven't 
already, it's worth looking at how Mirage2 changes on a computer vs. 
tablet vs. smartphone -- and even how it adapts to when you turn your 
tablet/smartphone on its side: https://atmire.com/preview/).

I know this doesn't answer your base question though, which is a good 
one. Not sure if anyone has done analysis of where researchers do their 
work, or even what devices DSpace end users are coming from.  I just 
wanted to point out that the more that we move to building responsive 
UIs (on frameworks like Bootstrap), the less the user device itself will 
matter (though we'll still need to ensure it obviously adapts to various 
screen sizes).

- Tim

[1] More on Mirage 2 for anyone interested:
 * https://atmire.com/website/?q=contributions/dspace-mirage-2
 * 
http://www.slideshare.net/bramluyten/mirage-2-a-responsive-user-interface-for-dspace

On 9/15/2014 8:14 AM, Mark H. Wood wrote:
 While we certainly ought to make good effort to support all users, a
 recent argument aroused my curiosity.  Are there statistics on just
 how much heavy-duty scholarship is being done using smartphones?



 --
 Want excitement?
 Manually upgrade your production database.
 When you want reliability, choose Perforce
 Perforce version control. Predictably reliable.
 http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk



 ___
 Dspace-general mailing list
 Dspace-general@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-general


--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] Important message from Google Scholar team - DSpace URL Redirects Issue

2014-09-17 Thread Tim Donohue

Hi all,

I'm forwarding on this message from Darcy Dapra at Google Scholar. If 
there are any questions or concerns, feel free to ask on this list. If 
we cannot answer them, we'll make sure to forward them on to the Google 
Scholar team for additional feedback.


- Tim

===

Hello!  I manage partnerships for Google Scholar. Among other things, I 
liaise with institutional repositories to help ensure that their 
collections are well-indexed in Google Scholar. For this, I have had 
opportunity to work with colleagues at DuraSpace (Hi Tim!) as well as at 
many universities.


Recently, web spam analyses here at Google have come across a DSpace 
customization/extension 
http://ukcorr.org/2012/03/22/using-google-analytics-statistics-within-dspace-3/ that 
has had the unfortunate side-effect of blocking indexing of full-text 
articles/theses. This extension redirected user clicks on bitstream URLs 
to the publications' landing pages. Based on conversations with some of 
the affected repositories, I understand that the goal of the redirection 
is to facilitate analytics for bitstream views. However, such 
redirection breaks the what-you-see-is-what-we-index model that web 
search services use and causes such URLs to be marked as cloaking/spam.


Colleagues at Edinburgh, University of Illinois and several other 
institutions have been really helpful in removing these redirects 
quickly from the repositories they manage. I would like to take this 
opportunity to thank them. We on the Scholar team have worked with web 
search folks here to ensure that these collections have been re-included 
as soon as possible.


If your repository includes either the earlier version of this extension 
or other code that redirects users from bitstream URLs to landing page 
URLs, I strongly recommend removing/disabling such redirects to avoid a 
similar situation.  Finally, we've worked with Tim to update the 
official DSpace indexing recommendations 
https://wiki.duraspace.org/display/DSDOC4x/Search+Engine+Optimization#SearchEngineOptimization-AvoidredirectingfiledownloadstoItemlandingpages 
to include this issue.


Many thanks,

Darcy

--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191iu=/4140/ostg.clktrk___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] DSpace 5.0 Release Candidate 3 is now available! DSpace 5.0 release coming in mid-January.

2014-12-22 Thread Tim Donohue
Hello All,

On behalf of the DSpace 5.0 Release Team and the Committers, I wanted to 
update the community around the status of the upcoming DSpace 5.0 
release. We were hoping to release 5.0 in early December, but our 
November Testathon uncovered a variety of minor bugs which we'd like to 
ensure are resolved in 5.0.

In the last month, we've been working hard to verify and fix all of the 
bugs which you (the Community) helped us to locate. The vast majority of 
them have now been resolved in a brand new 5.0 Release Candidate #3 
(5.0-rc3) version:

* Download 5.0-rc3 from: 
https://sourceforge.net/projects/dspace/files/DSpace%20Release%20Candidate/5.0-rc3/
* Checkout 5.0-rc3 (in GitHub) from: 
https://github.com/DSpace/DSpace/releases/tag/dspace-5.0-rc3
* 5.x Documentation: https://wiki.duraspace.org/display/DSDOC5x/

(For a list of all issues resolved in 5.0-rc3, please see our 5.0-rc3 
milestone in GitHub: 
https://github.com/DSpace/DSpace/pulls?q=milestone%3A5.0-RC3+is%3Aclosed )

As the end of year / holidays are approaching quickly, the DSpace 
Committers have decided to delay the final 5.0 Release until mid-January 
(tentatively January 15, 2015). This provides us all with more time to 
test out the new 5.0-rc3 pre-release for any final bugs, and more time 
to fix any last bugs that may be discovered along the way.

So, if you find yourself with some free time at work over the coming 
weeks, we encourage you to give 5.0-rc3 one last test run and let us 
know what you think!

* DSpace 5.0-rc3 is running on: http://demo.dspace.org/
* Or, you may install it locally by downloading it (see link above) or 
checking it out in GitHub ('dspace-5.0-rc3' tag).

As a reminder, the exciting new features in 5.0 are all detailed on our 
5.0 Release Status page:

https://wiki.duraspace.org/display/DSPACE/DSpace+Release+5.0+Status

We hope you all have a wonderful holiday and happy new year!

Tim Donohue, on behalf of the DSpace Committers

--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration  more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151iu=/4140/ostg.clktrk
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] ANNOUNCEMENT: DSpace 5 is Now Available!

2015-01-20 Thread Tim Donohue
 also be downloaded from:
http://www.dspace.org/latest-release/

5.0 ACKNOWLEDGMENTS

The DSpace application would not exist without the hard work and
support of the community. Thank you to the many developers who have
worked very hard to deliver all the new features and
improvements. Also thanks to the users who provided input and feedback
on the development, as well those who participated in the
testathons. Additionally we would like to thank Tim Donohue of
DuraSpace for ensuring that DSpace 5.0 went off without a hitch.

A detailed listing of all known people/institutions who contributed
directly to DSpace 5.0 is available in the Release Notes. If you
contributed and were accidentally not listed, please let us know so
that we can correct it!

For DSpace 5.0, we had a total of 56 individuals contribute code, bug
reports, and bug fixes. A big thanks goes out to everyone who
participated. We hope you'll continue to be a valuable addition to
the DSpace community for the next release and beyond!

MORE INFORMATION

More information on this release is also available in the DSpace 5.0
Release Notes at:

https://wiki.duraspace.org/display/DSDOC5x/Release+Notes

As always, we are happy to hear back from the community about DSpace.
Please let us know what you think of 5.0!

--
New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] [Dspace-tech] Advanced Search...

2015-02-17 Thread Tim Donohue

Hi Layale,

The Advanced Search option is no longer necessary if you are running 
DSpace with Discovery enabled. As of DSpace 4, the Discovery 
faceted/filtered search  browse is enabled by default. This is the main 
reason why we've removed that Advanced Search option from the user 
interface.

This Discovery feature combines many of the aspects of the advanced 
and simple search into a single interface. You can easily type in 
simple searches, and then filter the search results (look for the 
Advanced Filters link in the results) using much more advance techniques.

More info on the Discovery search interface is in the documentation at:
https://wiki.duraspace.org/display/DSDOC5x/Discovery

- Tim

On 2/16/2015 2:32 AM, Layale Bassil wrote:
 Hello All,

 Why I can’t find the “Advanced Search” link in my Dspace installed
 version 4.2 using the Mirage theme?

 Please advise whether I have to enable it somewhere?

 Thanks in advance,

 Regards.



 --
 Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
 from Actuate! Instantly Supercharge Your Business Reports and Dashboards
 with Interactivity, Sharing, Native Excel Exports, App Integration  more
 Get technology previously reserved for billion-dollar corporations, FREE
 http://pubads.g.doubleclick.net/gampad/clk?id=190641631iu=/4140/ostg.clktrk



 ___
 DSpace-tech mailing list
 dspace-t...@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-tech
 List Etiquette: 
 https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette


--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration  more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=190641631iu=/4140/ostg.clktrk
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] [Dspace-tech] Upgrading to version 4.3 in reponse to security advisory

2015-03-09 Thread Tim Donohue
Hi Alvin,

Based on the error, it sounds like you may be installing the 
dspace-4_x branch from GitHub? That dspace-4_x branch in GitHub has 
versions that look like 4.4-SNAPSHOT.

If you wanted to actually install DSpace 4.3, you'd want to use the 
tagged dspace-4.3 version in GitHub.

https://github.com/DSpace/DSpace/releases/tag/dspace-4.3

So, with git, you'd first need to checkout that tag into a new branch, e.g.

# Checks out the 4.3 tagged release into a new dspace-4.3 branch
git checkout dspace-4.3 -b dspace-4.3

Essentially, the error is occurring because all our dspace-x_x 
maintenance branches have a version ending in -SNAPSHOT. These 
SNAPSHOT versions don't exist in Maven Central (as they are not 
official DSpace releases).

While you *can* technically build/compile DSpace from that dspace-4_x 
maintenance branch, you'd need to *first* do so from the root source 
([dspace-source]), so that it auto-builds each and every 4.4-SNAPSHOT 
module for you locally. Your error is occurring cause you tried to first 
build from [dspace-source]/dspace and the 4.4-SNAPSHOT versions do not 
yet exist on your local system.

I hope that helps!

- Tim

On 3/9/2015 3:44 PM, Hutchinson, Alvin wrote:
 I have tried to run the update for our current DSpace (version 4.2) to 
 version 4.3 per the security notice below.

 However when I run [dspace-source]/dspace/mvn -U clean package (according to 
 the upgrade document) I see the following error:


 [INFO] DSpace Kernel :: Additions and Local Customizations  FAILURE [  2.345 
 s]
 snip
 . . .
 . . . .
 [ERROR] Failed to execute goal on project additions: Could not resolve 
 dependencies for project org.dspace.modules:additions:jar:4.4-SNAPSHOT: Could 
 not find artifact org.dspace:dspace-api:jar:4.4-SNAPSHOT in sonatype-releases 
 (https://oss.sonatype.org/content/repositories/releases/) - [Help 1]


 I can provide other details as necessary but from the error, I assume that 
 the executable should have been looking for 
 org.dspace.modules:additions:jar:4.3-SNAPSHOT rather than 4.4

 Or am I missing something?

 Alvin Hutchinson
 Smithsonian Libraries
 hutchins...@si.edu


 -Original Message-

 --

 Message: 2
 Date: Thu, 26 Feb 2015 11:30:21 -0600
 From: Tim Donohue tdono...@duraspace.org
 Subject: [Dspace-general] DSPACE SECURITY ADVISORY: New DSpace 5.1,
   4.3 and 3.4 releases resolve security issues in XMLUI and JSPUI
 To: dspace-general dspace-general@lists.sourceforge.net,
   dspace-tech dspace-t...@lists.sourceforge.net,dspace-devel
   dspace-de...@lists.sourceforge.net
 Message-ID: 54ef582d.7090...@duraspace.org
 Content-Type: text/plain; charset=utf-8; format=flowed


 All,

 In recent weeks, several security vulnerabilities where discovered in the 
 XMLUI and JSPUI of DSpace 3.x, 4.x and 5.x sites. Some of these 
 vulnerabilities also affect Space 1.x.x sites.

 While these security vulnerabilities vary in severity (see below), WE 
 RECOMMEND ALL DSPACE USERS CONSIDER UPGRADING TO EITHER DSPACE 3.4, 4.3 OR 
 5.1 to ensure your site is secure. Please note that the DSpace 5.1 release 
 also includes several minor bug fixes to the 5.x platform.

 * DSpace 5.1 Release Notes:
 https://wiki.duraspace.org/display/DSDOC5x/Release+Notes
 * DSpace 4.3 Release Notes:
 https://wiki.duraspace.org/display/DSDOC4x/Release+Notes
 * DSpace 3.4 Release Notes:
 https://wiki.duraspace.org/display/DSPACE/DSpace+Release+3.4+Notes

 Where possible, WE ALSO RECOMMEND IMMEDIATELY REMOVING ANY 
 allowLinking=true SETTINGS from your Tomcat Context configuration.
 Previously our DSpace installation documentation erroneously listed examples 
 which included allowLinking=true, while the Tomcat documentation details it 
 as a possible security concern [1]. The XMLUI Directory Traversal 
 Vulnerability (see below) is also exacerbated by having allowLinking=true 
 enabled.

 [NOTICE FOR DSPACE 1.x.x USERS:] Per our DSpace Software Support Policy [2], 
 all DSpace 1.x.x versions are now End-Of-Life (EOL). This includes versions 
 1.8.3 and below. As such, we will not be releasing any further 1.x.x versions 
 (even though several of these vulnerabilities do exist in 1.x.x versions). We 
 recommend either manually patching your instances or upgrading. If you are 
 considering an upgrade from DSpace 1.x.x, note that, as of DSpace 5, your 
 existing data (i.e. database contents, search/browse indexes) will now be 
 automatically upgraded from ANY prior version of DSpace (1.x.x, 3.x or 4.x). 
 Therefore, you may wish to consider upgrading directly to DSpace 5.1, as the 
 5.x upgrade process is simplified.

 
 Vulnerabilities Summary
 

 Summary of XMLUI Vulnerabilities:
 -

 [HIGH SEVERITY] XMLUI Directory Traversal Vulnerabilities: These 
 vulnerabilities allows someone to potentially access any file on your local 
 filesystem which is readable

[Dspace-general] DSPACE SECURITY ADVISORY: New DSpace 5.1, 4.3 and 3.4 releases resolve security issues in XMLUI and JSPUI

2015-02-26 Thread Tim Donohue

All,

In recent weeks, several security vulnerabilities where discovered in 
the XMLUI and JSPUI of DSpace 3.x, 4.x and 5.x sites. Some of these 
vulnerabilities also affect Space 1.x.x sites.

While these security vulnerabilities vary in severity (see below), WE 
RECOMMEND ALL DSPACE USERS CONSIDER UPGRADING TO EITHER DSPACE 3.4, 4.3 
OR 5.1 to ensure your site is secure. Please note that the DSpace 5.1 
release also includes several minor bug fixes to the 5.x platform.

   * DSpace 5.1 Release Notes: 
https://wiki.duraspace.org/display/DSDOC5x/Release+Notes
   * DSpace 4.3 Release Notes: 
https://wiki.duraspace.org/display/DSDOC4x/Release+Notes
   * DSpace 3.4 Release Notes: 
https://wiki.duraspace.org/display/DSPACE/DSpace+Release+3.4+Notes

Where possible, WE ALSO RECOMMEND IMMEDIATELY REMOVING ANY 
allowLinking=true SETTINGS from your Tomcat Context configuration. 
Previously our DSpace installation documentation erroneously listed 
examples which included allowLinking=true, while the Tomcat 
documentation details it as a possible security concern [1]. The XMLUI 
Directory Traversal Vulnerability (see below) is also exacerbated by 
having allowLinking=true enabled.

[NOTICE FOR DSPACE 1.x.x USERS:] Per our DSpace Software Support Policy 
[2], all DSpace 1.x.x versions are now End-Of-Life (EOL). This 
includes versions 1.8.3 and below. As such, we will not be releasing any 
further 1.x.x versions (even though several of these vulnerabilities do 
exist in 1.x.x versions). We recommend either manually patching your 
instances or upgrading. If you are considering an upgrade from DSpace 
1.x.x, note that, as of DSpace 5, your existing data (i.e. database 
contents, search/browse indexes) will now be automatically upgraded from 
ANY prior version of DSpace (1.x.x, 3.x or 4.x). Therefore, you may wish 
to consider upgrading directly to DSpace 5.1, as the 5.x upgrade process 
is simplified.


Vulnerabilities Summary


Summary of XMLUI Vulnerabilities:
-

[HIGH SEVERITY] XMLUI Directory Traversal Vulnerabilities: These 
vulnerabilities allows someone to potentially access any file on your 
local filesystem which is readable to the Tomcat user account. This 
includes files which are unrelated to DSpace or Tomcat, but are readable 
to all users on the filesystem (e.g. on Linux this includes /etc/passwd, 
/etc/hosts, etc). This also includes Tomcat configuration files (which 
may or may not contain passwords). These vulnerabilities have existed 
since DSpace 1.5.2. The initial vulnerability was discovered by Khalil 
Shreateh, with additional (related) vulnerabilities discovered by the 
Committer Team.

In some configurations of Tomcat, simply removing any 
allowLinking=true settings from your Tomcat's Context configuration 
will limit the directory traversal vulnerability's severity to only 
allow access to files within the XMLUI web application directory.

More information (and a patch) is available at 
https://jira.duraspace.org/browse/DS-2445 (Requires a DuraSpace JIRA 
account to access for two weeks, and then will be publicly available)


Summary of JSPUI Vulnerabilities:
-

[MEDIUM SEVERITY] JSPUI Directory Traversal Vulnerability: This 
vulnerability allows someone to potentially access any file within the 
JSPUI web application directory (e.g. WEB-INF/web.xml). This 
vulnerability is believed to have existed in all prior versions of 
DSpace, and was discovered by Khalil Shreateh.

More information (and a patch) is available at 
https://jira.duraspace.org/browse/DS-2448 (Requires a DuraSpace JIRA 
account to access for two weeks, and then will be publicly available)

[LOW SEVERITY] Cross-site scripting (XSS injection) is possible in JSPUI 
Recent Submissions listings. This vulnerability could allow a 
depositor/submitter to embed dangerous Javascript code into the metadata 
of a new submission, thus causing that code to be run across other user 
accounts. However, this vulnerability is only possible by someone with 
privileges to add content to your DSpace site. This vulnerability has 
existed since DSpace 1.5.x, and was discovered by Jean-Paul Zhao 
(University of Toronto).

More information is available at 
https://jira.duraspace.org/browse/DS-1702 (Requires a DuraSpace JIRA 
account to access for two weeks, and then will be publicly available)

[LOW SEVERITY] Cross-site scripting (XSS injection) is possible in JSPUI 
Discovery search form: This vulnerability could allow someone to embed 
dangerous Javascript code into links to search results. If a user was 
emailed such a link and clicked it, the javascript would be run in their 
local browser. This vulnerability has existed since DSpace 3.x. It was 
discovered on DSpace 4.x and 5.x by Gabriela Mircea (McMaster 
University) and Khalil Shreateh. It was discovered on DSpace 3.x by 
Ilyas Orak (Biznet Bilisim A.S.).

More information is 

Re: [Dspace-general] PDF Cover Pages Google Scholar - Search Engine inclusion implications

2015-06-19 Thread Tim Donohue
Hi All,

Anurag from Google Scholar is tracking this ongoing discussion. He's 
asked me to forward on this response from him.

---

Hi: I had reached out to Tim about DSpace support for PDF cover pages. I 
would like to thank him for initiating this discussion.

As I had mentioned in my talk, cover pages impact the effectiveness of 
all downstream automated systems that analyze PDF articles. This 
includes search services as well as personal collection managers such as 
Zotero, Mendeley, Papers etc that are widely used.

Given the diversity of layouts and structure, automated analysis  
metadata extraction from PDF articles is always a challenge. This is 
even more of a challenge if you consider that indexing systems need to 
run their algorithms over not just documents in specific repositories 
but all documents on the web.

Handling of PDF articles with cover pages is far more error-prone than 
that for original PDF. What happens to work today may no longer be able 
to work as algorithms are updated to handle the expanding diversity of 
layouts. We have seen this happen for several repositories :(

The concern that is most frequently mentioned as a reason for keeping 
cover pages is that the original PDF may not have sufficient/suitable 
information about where/how it was published. Which would keep it from 
being cited/referred to. However, pretty much no one tracks or cites 
articles or references by looking at the article by hand. For new 
articles, researchers use referencing tools like EndNote, bibtex etc and 
save structured bibliographic info from the article source.  Publisher 
sites, repositories, AIs, search services, all provide structured 
references in multiple formats. For older collections, the common 
approach, by far, is to use collection managers like Zotero, Mendeley, 
Papers. All of these depend on being able to analyze the PDF to automate 
the management. Making original PDF available as-is, with no changes, 
helps collection managers in the same way as it helps search services.

Based on my experience, I would recommend disabling automated cover 
pages - either front or back. The potential upside is no longer 
significant for most researchers. The potential downside, however, is 
pretty large -- impacting all downstream automated systems that make the 
research process easier.

I would like to thank the community for your consideration.

cheers,
anurag

--
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] PDF Cover Pages Google Scholar - Search Engine inclusion implications

2015-06-19 Thread Tim Donohue
Hi All,

First off, I just wanted to thank everyone for their thoughts, ideas, etc.

It's obvious that this is a very hot button topic in the DSpace 
community. My goal was to get the discussion started now, so that we can 
determine a way forward.

So, I'd encourage additional feedback on this topic. As of yet, there is 
no decision to remove this feature from DSpace. My goal in bringing this 
up is to ensure we are making a well informed decision on the benefits 
 detriments of PDF Cover Pages (and ensuring all of us are aware of 
both sides of the argument here).

While Google Scholar is not the only scholarly search engine out there, 
it is one of the ones I hear about most frequently from researchers and 
repository managers. At the very least, we should take into 
consideration this feedback from Google Scholar, as it definitely could 
have an effect on the visibility of DSpace PDFs in GS. So, at a minimum, 
this should help us to provide more informative warnings about some of 
the possible detriments of PDF cover pages.

If DCAT (DSpace Community Advisory Team) is interested in re-visiting 
this, it also may make for a good discussion at one of your monthly calls.

Thanks again all. Please do feel free to keep sending feedback!

- Tim

On 6/18/2015 11:23 AM, Tim Donohue wrote:
 Hi All,

 If you attended the Open Repositories 2015 (or followed along remotely),
 you may have heard about the Indexing Repositories: Pitfalls and Best
 Practices talk given by Anurag Acharya (co-creator of Google Scholar.

 If you haven't yet seen the talk, the slides are available at:
 http://www.or2015.net/wp-content/uploads/2015/06/or-2015-anurag-google-scholar.pdf


 The video should be available from the OR15 website in the coming weeks.

 One of the common indexing pitfalls mentioned by Anurag was
 automatically inserting PDF Cover Pages into PDFs. From what I can
 recall, there's a few reasons this can be problematic:

 1. Google Scholar (and possibly other search engines) attempts to
 extract metadata from the text of PDF (using some language processing
 and format identification techniques). This metadata includes
 auto-extracting title, abstract and author information from PDFs.
 Unfortunately, the addition of a PDF coverpage often breaks this
 metadata extraction, which may result in the document not appearing in
 Google Scholar.

 2. If all the PDF cover pages in your site look nearly identical (or
 completely identical), the Google Scholar indexer (and again possibly
 others) may wrongly flag the site for cloaking [1]. Essentially, it
 detects something is fishy as all the documents look very similar.
 This may result in the removal of the entire site from Google Scholar.

 So, to get to my question. In DSpace 5.0, we actually added a basic PDF
 Cover Page capability (which was requested by DCAT and others):
 https://wiki.duraspace.org/display/DSDOC5x/PDF+Citation+Cover+Page

 As this may have strong implications for inclusion in Google Scholar,
 should we consider removing this functionality from DSpace?

 For the time being, I've placed warnings in the Documentation for this
 feature to try to dissuade institutions from enabling it if Google
 Scholar inclusion is of high importance.

 This isn't really a technical issue (as we can easily remove code). But,
 I am interested in feedback from repository managers and users of DSpace
 to better inform our decisions on this feature going forward.

 Thanks,

 Tim

 [1] More on cloaking, which can be a spamming technique to trick
 search engines (and is therefore actively blocked by many search
 engines): https://en.wikipedia.org/wiki/Cloaking


--
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] training materials

2015-06-17 Thread Tim Donohue
Hi Jennifer (and all),

There are also some newer advanced DSpace training materials which 
cover how to customize DSpace, etc. They are from an early 2015 
Advanced DSpace Training session taught by James Creel and hosted by 
Texas Digital Library in Austin, Texas. While the course was called 
Advanced DSpace Training, it also covered topics like Installation and 
Configuration, etc. It specifically covered DSpace 4.2, but also 
introduced new DSpace 5.0 features (as that release had just come out).

Those materials (in the form of slides) are currently linked off the 
DSpace Resources wiki page (check the Customizing DSpace section, 
looking at the 2015 training links):

https://wiki.duraspace.org/display/DSPACE/DSpaceResources#DSpaceResources-Guides

Here's the direct links:
http://www.slideshare.net/DuraSpace/dspace-42-basics-configuration
http://www.slideshare.net/DuraSpace/dspace-42-transmission-importexport
http://www.slideshare.net/DuraSpace/dspace-42-xmlui-theming
http://www.slideshare.net/DuraSpace/dspace-50-feature-preview

- Tim


On 6/16/2015 2:11 PM, LEWIS Stuart wrote:
 Hi Jennifer,

 Most of the concepts that the course will still be relevant: for example
 communities and collections, items, deposit configuration, and some
 JSPUI customisation options.

 Some of the options, for example how to configure DSpace to use LDAP or
 Shibboleth authentication, or how to run import and export commands,
 will be similar, but the exact commands will have changed a little.  So
 it might be good to also have the online DSpace manual handy:

   - https://wiki.duraspace.org/display/DSPACE/Documentation

 And some features, for example the XMLUI user interface or solr
 discovery are newer and won't feature in the course.

 If you ever have specific questions, please don't hesitate to email the
 DSpace technical email list:

   - https://lists.sourceforge.net/lists/listinfo/dspace-tech

 Thanks,


 Stuart Lewis (one of the original creators of the DSpace course you
 reference!)
 Head of Research and Learning Services
 Deputy Director Library  University Collections, Information Services
 University of Edinburgh
 stuart.le...@ed.ac.uk mailto:stuart.le...@ed.ac.uk

 From: Ho, Jennifer j...@cct.org mailto:j...@cct.org
 Date: Tuesday, 16 June 2015 16:10
 To: dspace-general@lists.sourceforge.net
 mailto:dspace-general@lists.sourceforge.net
 dspace-general@lists.sourceforge.net
 mailto:dspace-general@lists.sourceforge.net
 Subject: [Dspace-general] training materials

 Hello:

 I have just had dspace installed on my machine. Links on dspace.org sent
 me to a training course here
 http://cadair.aber.ac.uk/dspace/handle/2160/615. It looks nice and
 thorough but was last updated in 2008. Could anybody tell me if the
 course is still mostly relevant, and/or if there are other training
 resources you’d recommend? Many thanks.

 Jennifer

 Macintosh
 HD:Users:computer1:Desktop:Brooks_Desktop_042715:_Trust:layout:Trust_esig_050515:images:Trust_logo_horizontal_esig.png
 http://www.cct.org/

 *Jennifer ho
 */Digital Archivist /**

 /–/

 225 N. Michigan Avenue
 Suite 2200
 Chicago, IL 60601

 TEL  312.616.8000 ext 258
 FAX  312.616.7955
 TTY  312.856.1703

 www.cct.org http://www.cct.org



 The University of Edinburgh is a charitable body, registered in
 Scotland, with registration number SC005336.



 --



 ___
 Dspace-general mailing list
 Dspace-general@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/dspace-general


--
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] Watch the DSpace Roadmap talk, send us your feedback, get involved!

2015-06-17 Thread Tim Donohue
Hi All,

If you were unable to attend the DSpace Interest Group sessions at 
either OR15 (in Indianapolis last week) or OAI9 (in Geneva yesterday), 
you may have heard some talk on Twitter and mailing lists about the 
DSpace Technology Roadmap (for 2015-2016) which was presented at those 
conferences.

The video of this Roadmap talk (~25 minutes) is now available on YouTube:

http://youtu.be/qlPAeqCptxw

The slides are available at:

http://www.slideshare.net/tdonohue/dspace-technology-roadmap-201516

The Roadmap itself is publicly documented on the Wiki at:

https://wiki.duraspace.org/display/DSPACE/RoadMap

If you are interested in where DSpace is going in the next few years, 
I'd highly recommend reviewing the Roadmap and providing us with any 
feedback you may have. Feedback can be provided (anonymously if you 
wish) at http://tinyurl.com/dspacefeedback2015 or via the #dspaceplan 
hashtag on Twitter.

We are also still actively looking for institutions to participate in 
the Roadmap by donating (part-time) developers to the cause or joining 
as a DuraSpace Member (http://duraspace.org/become_a_member).

Please get in touch, if you are interested in a more active role. Your 
institution will be recognized for your efforts, and your developer(s) 
may end up being nominated as future DSpace Committers.

If there are any questions regarding the RoadMap or the Strategic Plan, 
I'm happy to answer them on or off list.

Tim


-- 
Tim Donohue
Technical Lead for DSpace  DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org

--
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] DSpace UI Working Group Meeting, Tomorrow (Aug 25) @ 15:00 UTC

2015-08-24 Thread Tim Donohue

All,

A reminder that the second meeting of the DSpace UI Working Group is 
TOMORROW (Tues, Aug 25) at 15:00 UTC (11:00am EDT).  Connection 
information is below.


Anyone is welcome to attend and join this new working group. A working 
group charter, with deliverables, is available at 
https://wiki.duraspace.org/display/DSPACE/DSpace+UI+Working+Group


Meeting Agenda:

 * Updates on Deliverable #2 - Pilot application expectations/requirements.
 o Draft document:
   
https://docs.google.com/document/d/1b6LkuHdO9f6Z9dubU-ZPTWsiF-2brMZsuqa-LE3Z7Qg/edit?usp=sharing
 * Updates on Deliverable #3 - Criteria for evaluating pilot applications
 o Draft document:
   https://wiki.duraspace.org/display/DSPACE/DSpace+UI+Criteria
 * Are we ready to begin recruiting pilot teams?
 * Next meeting?


Dial in via toll-free landline:

 * /U.S.A/Canada toll free/: 866-740-1260, participant code: 2257295
 * /International toll free/: http://www.readytalk.com/intl
 o Use the above link and input 2257295 and the country you are
   calling from to   get your  country's toll-free dial-in number
 o Once on the call, enter participant code 2257295


As always, meeting notes will be made available off the working group's 
wiki page.


Thanks,

Tim Donohue

--
Tim Donohue
Technical Lead for DSpace  DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org

--
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] NOTICE: dspace-general will move to Google Groups TOMORROW (Tues, Aug 25) - ACTION REQUIRED

2015-08-24 Thread Tim Donohue

Hello dspace-general subscribers,

This dspace-general SourceForge mailing list will be migrated to Google 
Groups TOMORROW (Tues, Aug 25) at approximately 19:00 UTC (3pm EDT). 
During this migration, the mailing list will also be renamed 
dspace-community, but it's purpose/role will remain the same.


Unfortunately, because of Google Group's strict policies to avoid 
spammers, we will be UNABLE to migrate your subscription on your 
behalf.  But, all dspace-general mailing list archives will be migrated 
automatically to the new location.


ACTION REQUIRED: Once the mailing list is migrated, you will need to 
re-subscribe yourself to the new dspace-community Google Group. At 
that point, a final notice will be sent to all subscribers of this 
SourceForge list, detailing how to quickly join the new mailing list. 
Your email address will also be unsubscribed from the retired 
SourceForge mailing list.


OPTIONALLY, if you want to get a jump on things (and ensure you don't 
miss a message), you may immediately send a join request via one of 
these routes:
* Email /dspace-community+subscr...@googlegroups.com /You'll receive an 
email response that tells you to either *reply* to submit your join 
request, or click a link.
* OR visit https://groups.google.com/d/forum/dspace-community and click 
Apply to join group (You must be logged in to see that button)
Submitting a Join Request will ensure you are immediately subscribed 
to the new mailing list once the migration is completed.


This migration from SourceForge to Google Groups is taking place for the 
following reasons:
1) SourceForge hosting has been unstable recently. Our SF-hosted mailing 
lists have gone down twice in the last six months.

2) Google Groups provides better list search and management capabilities.
3) Other DuraSpace projects use Google Groups and have had good 
experiences with it.


Thanks,

Tim Donohue

--
Tim Donohue
Technical Lead for DSpace  DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org

--
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] Invitation to join the DSpace User Interface (UI) Working Group, Aug 10 @ 15:00 UTC

2015-08-03 Thread Tim Donohue

Hello all,

Based on the recently approved Roadmap [1], we are about to kick off a 
new working group to oversee the DSpace User Interface (UI) replacement 
project. We are extending an invitation to any interested community 
members to join this working group or take part in UI pilots.


The working group will be of limited duration. Its mission is not to 
develop the replacement UI, but rather to manage the process of 
reviewing the alternatives, comparing brief pilot demonstrations, and 
establishing the selection process of an architecture and technology for 
the new UI.  The work of developing the pilot UI demonstrations will be 
done by volunteers, and a call for pilot project teams will be made in 
the coming weeks.  Members of the working group may choose to join one 
of the pilot teams, but that is not required.


The draft of the working group charter is available for you to review here:
https://wiki.duraspace.org/display/DSPACE/DSpace+UI+Working+Group

The first meeting of this UI Working Group will take place on Monday, 
August 10th at 15:00 UTC (11:00am EDT). Connection information is below.


Dial in via toll-free landline:

 * /U.S.A/Canada toll free/:
   866-740-1260tel:866-740-1260, participant code: 2257295
 * /International toll free/:
   
http://www.readytalk.com/intlhttp://r20.rs6.net/tn.jsp?e=001bG8maQmhqwSVNusd98lSqz6q2LsqBf2hC8sCtIxxii1iqoa9ahDM8ljiwuF-E9XRRev87FIuzGD0zHbeLY_hf9iMV2pNuhdn29iA2gcCZV_oAVEwO_9ANwYWHLJzvmcn
 o Use the above link and input 2257295 and the country you are
   calling from to   get your  country's toll-free dial-in number
 o Once on the call, enter participant code 2257295

If you are interested in joining this Working Group, or taking part in 
one of the pilots, please consider attending this session.  Notes from 
the session will be made available off the working group charter (linked 
above).


Thanks,

Tim Donohue

[1] DSpace RoadMap: https://wiki.duraspace.org/display/DSPACE/RoadMap

--
Tim Donohue
Technical Lead for DSpace  DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org

--
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] Invitation to join the DSpace User Interface (UI) Working Group, Aug 10 @ 15:00 UTC

2015-08-11 Thread Tim Donohue

Hi all,

The meeting notes from this initial UI Working Group meeting are now 
posted at:


https://wiki.duraspace.org/display/DSPACE/2015-08-10+UI+Working+Group+Meeting+notes

The next UI Working Group meeting is scheduled for *Tues, August 25 at 
15:00UTC (11:00am EDT).*  Anyone is welcome to attend.


We still welcome new members to this UI Working Group.  If you are 
interested in helping immediately with one of the deliverables, get in 
touch with a member of one of the sub groups (see meeting notes). Or, 
just show up at our next meeting.


Thanks,

Tim Donohue

On 8/3/2015 3:15 PM, Tim Donohue wrote:

Hello all,

Based on the recently approved Roadmap [1], we are about to kick off a 
new working group to oversee the DSpace User Interface (UI) 
replacement project. We are extending an invitation to any interested 
community members to join this working group or take part in UI pilots.


The working group will be of limited duration. Its mission is not to 
develop the replacement UI, but rather to manage the process of 
reviewing the alternatives, comparing brief pilot demonstrations, and 
establishing the selection process of an architecture and technology 
for the new UI.  The work of developing the pilot UI demonstrations 
will be done by volunteers, and a call for pilot project teams will be 
made in the coming weeks.  Members of the working group may choose to 
join one of the pilot teams, but that is not required.


The draft of the working group charter is available for you to review 
here:

https://wiki.duraspace.org/display/DSPACE/DSpace+UI+Working+Group

The first meeting of this UI Working Group will take place on Monday, 
August 10th at 15:00 UTC (11:00am EDT). Connection information is below.


Dial in via toll-free landline:

  * /U.S.A/Canada toll free/: 866-740-1260, participant code: 2257295
  * /International toll free/: http://www.readytalk.com/intl
  o Use the above link and input 2257295 and the country you are
calling from to   get your  country's toll-free dial-in number
  o Once on the call, enter participant code 2257295

If you are interested in joining this Working Group, or taking part in 
one of the pilots, please consider attending this session.  Notes from 
the session will be made available off the working group charter 
(linked above).


Thanks,

Tim Donohue

[1] DSpace RoadMap: https://wiki.duraspace.org/display/DSPACE/RoadMap
--
Tim Donohue
Technical Lead for DSpace  DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org


--
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


Re: [Dspace-general] NOTICE: dspace-general will move to Google Groups TOMORROW (Tues, Aug 25) - ACTION REQUIRED

2015-08-25 Thread Tim Donohue

Hello dspace-general subscribers,

REMINDER: In just a few short hours (approximately 19UTC / 3pm EDT), 
this 'dspace-general' SourceForge mailing list will be migrated to a new 
'dspace-community' Google Group.


At 19UTC, the following will occur:
1. Any future emails sent to dspace-general@lists.sourceforge.net will 
bounce back and refer you to the new mailing list.
2. Emails from the last few days will be migrated to the new Google 
Group (most of the archives have already been migrated).

3. The new 'dspace-community' Google Group will be activated.
4. Anyone who has already submitted a Join Request (see email below) 
will be signed up immediately. There's still time to submit it!
5. A final notice will be sent to this old SourceForge mailing list 
redirecting everyone else to sign up for the new mailing list.
6. Everyone will be automatically unsubscribed from this old SourceForge 
mailing list.


Thanks! We hope to see you on the new dspace-commun...@googlegroups.com 
mailing list in just a few short hours!


- Tim

On 8/24/2015 12:43 PM, Tim Donohue wrote:

Hello dspace-general subscribers,

This dspace-general SourceForge mailing list will be migrated to 
Google Groups TOMORROW (Tues, Aug 25) at approximately 19:00 UTC (3pm 
EDT). During this migration, the mailing list will also be renamed 
dspace-community, but it's purpose/role will remain the same.


Unfortunately, because of Google Group's strict policies to avoid 
spammers, we will be UNABLE to migrate your subscription on your 
behalf.  But, all dspace-general mailing list archives will be 
migrated automatically to the new location.


ACTION REQUIRED: Once the mailing list is migrated, you will need to 
re-subscribe yourself to the new dspace-community Google Group. At 
that point, a final notice will be sent to all subscribers of this 
SourceForge list, detailing how to quickly join the new mailing list. 
Your email address will also be unsubscribed from the retired 
SourceForge mailing list.


OPTIONALLY, if you want to get a jump on things (and ensure you don't 
miss a message), you may immediately send a join request via one of 
these routes:
* Email /dspace-community+subscr...@googlegroups.com /You'll receive 
an email response that tells you to either *reply* to submit your 
join request, or click a link.
* OR visit https://groups.google.com/d/forum/dspace-community and 
click Apply to join group (You must be logged in to see that button)
Submitting a Join Request will ensure you are immediately subscribed 
to the new mailing list once the migration is completed.


This migration from SourceForge to Google Groups is taking place for 
the following reasons:
1) SourceForge hosting has been unstable recently. Our SF-hosted 
mailing lists have gone down twice in the last six months.

2) Google Groups provides better list search and management capabilities.
3) Other DuraSpace projects use Google Groups and have had good 
experiences with it.


Thanks,

Tim Donohue

--
Tim Donohue
Technical Lead for DSpace  DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org


--
Tim Donohue
Technical Lead for DSpace  DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org

--
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general


[Dspace-general] NOTICE: DSpace General list moved to Google Groups. Please RESUBSCRIBE yourself!

2015-08-25 Thread Tim Donohue

Hello dspace-general subscribers,

The migration of the dspace-general list archives from SourceForge to 
the 'dspace-community' Google Group has succeeded. As mentioned 
previously, we are UNABLE to migrate your subscription to this mailing 
list.


From this point forward, please use dspace-commun...@googlegroups.com
https://groups.google.com/d/forum/dspace-community

If you haven't already, you must RESUBSCRIBE in order to continue to 
receive emails from this DSpace mailing list.


TO RESUBSCRIBE to dspace-community, please choose one of the following 
options:

* Send an email to /dspace-community+subscr...@googlegroups.com/
* OR, visit https://groups.google.com/d/forum/dspace-community and click 
Join Group at the top. You can then also modify your subscription 
options (digest mode, etc)


This will be the FINAL email sent across the dspace-general SourceForge 
mailing list.  To continue to receive DSpace General emails, you must 
subscribe yourself to the new dspace-community Google Group.


We hope to see you on dspace-commun...@googlegroups.com!

Sincerely,

Tim

--
Tim Donohue
Technical Lead for DSpace  DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org

--
___
Dspace-general mailing list
Dspace-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-general