[Dspace-devel] DSpace 1.7.0 to be released on Dec 17, just in time for holidays

[Peter Dietz]

All,

The Committers would like to formally announce that the much anticipated
DSpace 1.7.0 will be released on Friday, December 17, 2010.

The recent DSpace 1.7.0 Testathon has been a success. It has helped us to
locate several issues/bugs that we are working to resolve before the 1.7.0
Final Release. We'd like to thank everyone who has taken part in testing and
reporting of issues.

As a reminder, this new release will bring several new major features, along
with numerous bug fixes and performance improvements.

Major new features/improvements include:
* A new XMLUI Theme named Mirage (contributed by @mire), which you can see
in action at http://demo.dspace.org/xmlui/
* The DSpace "Discover" module, which allows you to add faceted
browsing/searching to XMLUI (contributed by @mire), also in action at
http://demo.dspace.org/xmlui/
* A new Archival Information Package (AIP) Backup & Restore process
* A new Curation Administration User Interface -- which will allow for a
series of Curation tasks to be performed on objects in DSpace.
* PowerPoint text extraction, for searching within PowerPoint slides
* Improved Google Scholar Indexing -- We've been working directly with
Google Scholar developers to ensure your DSpace contents are findable in
Google Scholar.
* Improved performance and scalability of DSpace (thanks to Graham Triggs
for leading the effort to plug up memory leaks and fix other performance
issues)
* Automated Unit Testing of core code -- helps the developers ensure the
core code of DSpace is as bug free and stable as possible

In the meantime, you are welcome to try out the early release of DSpace
1.7.0 on http://demo.dspace.org/ and continue to provide any early feedback
you may have. If you'd like to install a test version on your own server,
early releases of DSpace 1.7.0 are also available to download on
SourceForge: http://sourceforge.net/projects/dspace/files/

More information on this release is also available in the DSpace 1.7.0
Release Notes at:
https://wiki.duraspace.org/display/DSPACE/DSpace+Release+1.7.0+Notes

We hope that you are as excited as we are about the upcoming release of
DSpace 1.7.0.  Have a happy holiday season!

Peter Dietz (1.7.0 Release Coordinator) and the DSpace Committers
--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel

[Dspace-devel] DSpace Developers Meeting Canceled, upcoming 1.7.0 schedule

[Tim Donohue]

Hi All,

This week's DSpace Developers Meeting (Weds Nov 24) is canceled.  As 
this is Thanksgiving week in the USA, we're taking the week off.

However, you all should be aware of the upcoming DSpace 1.7.0 Release 
Schedule:

* December 3 : Release Candidate 2 will be released
* December 6-15 : Final Testing / Bug Fixing
* December 17 : Final 1.7.0 Release

Peter Dietz already put out a separate call for everyone to wrap up your 
1.7.0 JIRA issues, or reschedule them.  See his message for more:

http://www.mail-archive.com/dspace-devel@lists.sourceforge.net/msg04959.html

Committers, please take some time to review all JIRA issues assigned to 
you, and either close them out, or reschedule them for the next release. 
  In addition, if you have any extra time, feel free to claim one of the 
last unclaimed issues scheduled for 1.7.0.  Any which remain unclaimed 
will need to be rescheduled for post-1.7.0.  Here's the list of 
currently unclaimed 1.7.0 issues in JIRA:

https://jira.duraspace.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+DS+AND+resolution+%3D+Unresolved+AND+assignee+is+EMPTY+AND+fixVersion+%3D+%221.7.0%22+ORDER+BY+created+ASC

We'll resume our DSpace Developers Meetings next week. Have a great 
holiday!

- Tim

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

--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Re: [Dspace-devel] Do we want to continue to maintain a CHANGES file in SVN?

[Kim Shepherd]

I like the new DSDOC history.

My only concern is missing out on properly attributing patch authors when
they're neither the reporter nor the committer, which does happen. Is there
a way we can add an extra "contributor" field to a JIRA ticket before we
resolve/close it so that our "History" page keeps a track of the patch
author as well as the reporter and the committer?

Cheers,

Kim

On 19 November 2010 05:31, Tim Donohue  wrote:

> All,
>
> As we now are tracking all issues via JIRA and are going to be releasing
> our Documentation via Confluence (which integrates well with JIRA), I'm
> beginning to wonder whether we need to continue to maintain a CHANGES
> file in SVN:
>
> http://scm.dspace.org/svn/repo/dspace/trunk/dspace/CHANGES
>
> In preparation for 1.7.0 release, I've recently updated our new
> "History" page in our Wiki Docs to automatically query for all 1.7.0
> fixed issues in JIRA.  This essentially provides a very similar list to
> what we have been maintaining in the CHANGES file.  But, now it is
> automated, based on JIRA issues which are closed/resolved for 1.7.0:
>
> https://wiki.duraspace.org/display/DSDOC/History
>
> So, I thought I'd ask to see if anyone feels strongly about continuing
> to maintain the CHANGES file.  There are a few options going forward:
> (1) Continue to maintain CHANGES file in parallel to this new History page.
> (2) Keep the CHANGES file in SVN, but replace all its contents with just
> a link to 'History' page in the Wiki Documentation.
> (3) Remove the CHANGES file from SVN entirely, as the changes/history
> are now tracked automatically in the Wiki docs.
>
> I am beginning to lean more and more towards #2.  But, if others feel
> strongly about continuing to maintain the CHANGES file, we can do so.
>
> What do you think?
>
> - Tim
>
>
> --
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2 & L3.
> Spend less time writing and  rewriting code and more time creating great
> experiences on the web. Be a part of the beta today
> http://p.sf.net/sfu/msIE9-sfdev2dev
> ___
> Dspace-devel mailing list
> Dspace-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dspace-devel
>
--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel

[Dspace-devel] [DuraSpace JIRA] Updated: (DS-613) Error Handling in the XMLUI interface after section expired

[Tim Donohue (DuraSpace JIRA)]

 [ 
https://jira.duraspace.org/browse/DS-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tim Donohue updated DS-613:
---

Attachment: xmlui-invalid-continuation.patch

Attached a patch (xmlui-invalid-continuation.patch) which makes some small 
improvements to this "Invalid Continuation" error message.

The patch does two main things:
(1) Changes the Header of that error page to say "Your Session has Expired".  
This is a slightly more meaningful message than "Invalid Continuation".
(2) It also adds a "Go to DSpace home" link at the top of the error page.  That 
way there is an easy way off the error page.

Besides that, the error page remains the same.  So, this isn't a significant 
fix, and may not be perfect.  But, it's a quick fix that still seems doable in 
1.7.0.

Comments/thoughts/suggestions welcome.

> Error Handling  in the XMLUI interface after section expired
> 
>
> Key: DS-613
> URL: https://jira.duraspace.org/browse/DS-613
> Project: DSpace
>  Issue Type: Improvement
>  Components: XMLUI
>Affects Versions: 1.6.0
> Environment: apache-tomcat-6.0.18
> jdk1.6.0_13
> Debian GNU Linux 5.0 
>Reporter: Antero Neto
>Assignee: Tim Donohue
>Priority: Major
> Fix For: 1.7.0
>
> Attachments: invalid-continuation.jpeg, 
> xmlui-invalid-continuation.patch
>
>
> When editing metadata  if the user is away long enough to the section expire, 
> the return is a cocoon "invalid continuation" error.
> See attached print.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel

[Dspace-devel] [DuraSpace JIRA] Updated: (DS-552) Servlet to deliver repository size statistics

[Mark H. Wood (DuraSpace JIRA)]

 [ 
https://jira.duraspace.org/browse/DS-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mark H. Wood updated DS-552:


Fix Version/s: (was: 1.7.0)

> Servlet to deliver repository size statistics
> -
>
> Key: DS-552
> URL: https://jira.duraspace.org/browse/DS-552
> Project: DSpace
>  Issue Type: New Feature
>  Components: DSpace API
>Reporter: Mark H. Wood
>Assignee: Mark H. Wood
> Attachments: stats.patch
>
>
> A tiny servlet to return counts of bitstreams, items, collections, and 
> communities, and the amount of storage occupied.  The attached patch also 
> maps it into both JSPUI and XMLUI at /content-statistics.
> The returned "page" is an XML document.  For now, see the package.html 
> changes in the patch.  I'll update the end-user documentation presently.
> We use an earlier version of this with 1.5.1 as input to our library 
> "dashboard", which gathers statistics on various services for quick reference.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel

[Dspace-devel] [DuraSpace JIRA] Closed: (DS-590) New INSTALL event when an Item is approved

[Mark H. Wood (DuraSpace JIRA)]

 [ 
https://jira.duraspace.org/browse/DS-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mark H. Wood closed DS-590.
---


> New INSTALL event when an Item is approved
> --
>
> Key: DS-590
> URL: https://jira.duraspace.org/browse/DS-590
> Project: DSpace
>  Issue Type: Improvement
>  Components: DSpace API
>Reporter: Mark H. Wood
>Assignee: Mark H. Wood
> Fix For: 1.7.0
>
>
> There appears to be no way to discover that a new Item has been accepted.  We 
> can, for example, do backup more intelligently if we know that there is 
> something new to back up.
> This change creates a new Event type INSTALL, which is fired when an Item is 
> installed into the repository proper.  That is:  when it moves from a 
> Workspace or Workflow to a Collection.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel

[Dspace-devel] [DuraSpace JIRA] Closed: (DS-633) NPE when deleting object returned by EPerson.findAll()

[Mark H. Wood (DuraSpace JIRA)]

 [ 
https://jira.duraspace.org/browse/DS-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mark H. Wood closed DS-633.
---


> NPE when deleting object returned by EPerson.findAll()
> --
>
> Key: DS-633
> URL: https://jira.duraspace.org/browse/DS-633
> Project: DSpace
>  Issue Type: Bug
>  Components: DSpace API
>Affects Versions: 1.6.2, 1.7.0
>Reporter: Mark H. Wood
>Assignee: Mark H. Wood
>Priority: Critical
> Fix For: 1.7.0
>
> Attachments: DatabaseManager.patch, EPerson.patch
>
>
> While building a test tool to purge all users from the database, I ran into 
> persistent NPEs on EPerson.delete().  This seems to result from 
> EPerson.findAll() using DatabaseManager.query(), which does not set the table 
> type into the returned TableRowIterator.  DatabaseManager.delete() needs to 
> know the table type in order to look up the table's primary key.  Kaboom.
> It appears that query() is meant for use with queries whose result is not a 
> base table type (JOINs and the like).  For a simple SELECT * FROM table... it 
> seems that queryTable() should be used.  The attachment EPerson.patch makes 
> this change everywhere in EPerson that it seems to be appropriate and is 
> observed to eliminate the NPEs in this specific case.  (The patch also tidies 
> some comments.)
> The attachment DatabaseManager.patch is to defend against deletion of untyped 
> rows and throw a more descriptive exception.  The class might benefit from 
> more extensive antibugging work.  This patch is not essential but might be 
> helpful in similar circumstances.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel

[Dspace-devel] [DuraSpace JIRA] Closed: (DS-618) Recommended versions of prerequisites becoming outdated

[Mark H. Wood (DuraSpace JIRA)]

 [ 
https://jira.duraspace.org/browse/DS-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mark H. Wood closed DS-618.
---


> Recommended versions of prerequisites becoming outdated
> ---
>
> Key: DS-618
> URL: https://jira.duraspace.org/browse/DS-618
> Project: DSpace
>  Issue Type: Task
>  Components: Documentation
>Reporter: Mark H. Wood
>Assignee: Mark H. Wood
> Fix For: 1.7.0
>
>
> We still recommend at least "PostgreSQL 7.3 or 7.4".  7.4 is now seven years 
> old and losing maintainer support next month (or so).  By December only 8.2 
> and up will be supported.
> Sun Java 5 SE reaches its End Of Service Life in October 2010.
> Maven 2.2 is current.  We might recommend at least 2.0.11 (the current "older 
> release") rather than 2.0.8.
> Tomcat 4 is positively ancient and definitely unsupported by its maintainers. 
>  Even 5.0 is too old for help.  5.5 should be our minimum recommendation.
> Please discuss.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel

[Dspace-devel] [DuraSpace JIRA] Closed: (DS-494) DatabaseManager.process() unnecessarily limits range of DECIMAL or NUMERIC

[Mark H. Wood (DuraSpace JIRA)]

 [ 
https://jira.duraspace.org/browse/DS-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mark H. Wood closed DS-494.
---


> DatabaseManager.process() unnecessarily limits range of DECIMAL or NUMERIC
> --
>
> Key: DS-494
> URL: https://jira.duraspace.org/browse/DS-494
> Project: DSpace
>  Issue Type: Bug
>  Components: DSpace API
>Affects Versions: 1.5.2, 1.6.0
> Environment: PostgreSQL
>Reporter: Mark H. Wood
>Assignee: Mark H. Wood
> Fix For: 1.7.0
>
> Attachments: DatabaseManager.patch, DS-494.patch
>
>
> INTEGER, DECIMAL, and NUMERIC are lumped together.  In the case we are using 
> Oracle, the code will set the column to an int or a long depending on the 
> size of the value.  (I would like to know why we bother.)  Otherwise the 
> value is assumed to be within the range of int.  But DECIMAL and NUMERIC can 
> be far larger than int, and are returned by e.g. sum(BIGINT).
> The attached patch widens the result, in the non-Oracle case, to long for all 
> three SQL datatypes.  Strictly speaking, DECIMAL and NUMERIC should be mapped 
> to java.math.BigDecimal, but that requires the introduction of new methods to 
> TableRow as well.  Widening from int to long probably covers most of the 
> real-world cases.  The patch is against 1.5.2 but also applies to 1.6.0-rc2.
> I would appreciate comments on how this widening may affect other code.  The 
> patch is in test on a live system, but in a locally-developed webapp rather 
> than any of the main DSpace UIs.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel

[Dspace-devel] [DuraSpace JIRA] Commented: (DS-768) All XMLUI Error Pages respond with 200 OK, instead of 404 Not Found

[Tim Donohue (DuraSpace JIRA)]

[ 
https://jira.duraspace.org/browse/DS-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18241#action_18241
 ] 

Tim Donohue commented on DS-768:


We seem to be experiencing this Cocoon Bug: 
https://issues.apache.org/jira/browse/COCOON-2218

If I switch all 404 response codes (in main /src/main/webapps/sitemap.xmap) to 
instead return 500 (or any other response code), then everything works as 
planned.  Only the 404 responses seem to be affected by this problem.

This Cocoon bug seems to have been resolved in the current Cocoon 2.2 Trunk 
code, but was never officially released in a stable version of Cocoon.

> All XMLUI Error Pages respond with 200 OK, instead of 404 Not Found
> ---
>
> Key: DS-768
> URL: https://jira.duraspace.org/browse/DS-768
> Project: DSpace
>  Issue Type: Bug
>  Components: XMLUI
>Affects Versions: 1.6.0, 1.6.1, 1.6.2, 1.7.0
>Reporter: Tim Donohue
>Priority: Major
> Fix For: 1.7.0
>
>
> In DSpace 1.7.0 RC1, the XMLUI "Page Not Found" page responds with a 200 OK, 
> rather than the necessary 404 Not Found error.
> For example:
> http://demo.dspace.org/xmlui/NOTAVALIDPATH
> I believe this used to function properly in 1.6.x, but it seems to be broken 
> now.
> Obviously, we want this to return a 404 Not Found, in order to ensure that 
> search engines do not index "Page Not Found" responses.
> Furthermore, it has been discovered that all other XMLUI Error pages (Cocoon 
> Errors or Invalid Continuation errors) also respond with 200 OK.  In 
> addition, it seems this affects all 1.6.x versions of DSpace, as the same 
> responses can be found on http://dspace.mit.edu (currently running 1.6.0 with 
> patches), and http://researchspace.auckland.ac.nz (currently running 1.6.2 
> with patches).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel

[Dspace-devel] [DuraSpace JIRA] Updated: (DS-768) All XMLUI Error Pages respond with 200 OK, instead of 404 Not Found

[Tim Donohue (DuraSpace JIRA)]

 [ 
https://jira.duraspace.org/browse/DS-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tim Donohue updated DS-768:
---

Status: Open  (was: Received)

> All XMLUI Error Pages respond with 200 OK, instead of 404 Not Found
> ---
>
> Key: DS-768
> URL: https://jira.duraspace.org/browse/DS-768
> Project: DSpace
>  Issue Type: Bug
>  Components: XMLUI
>Affects Versions: 1.6.0, 1.6.1, 1.6.2, 1.7.0
>Reporter: Tim Donohue
>Priority: Major
> Fix For: 1.7.0
>
>
> In DSpace 1.7.0 RC1, the XMLUI "Page Not Found" page responds with a 200 OK, 
> rather than the necessary 404 Not Found error.
> For example:
> http://demo.dspace.org/xmlui/NOTAVALIDPATH
> I believe this used to function properly in 1.6.x, but it seems to be broken 
> now.
> Obviously, we want this to return a 404 Not Found, in order to ensure that 
> search engines do not index "Page Not Found" responses.
> Furthermore, it has been discovered that all other XMLUI Error pages (Cocoon 
> Errors or Invalid Continuation errors) also respond with 200 OK.  In 
> addition, it seems this affects all 1.6.x versions of DSpace, as the same 
> responses can be found on http://dspace.mit.edu (currently running 1.6.0 with 
> patches), and http://researchspace.auckland.ac.nz (currently running 1.6.2 
> with patches).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel

[Dspace-devel] [DuraSpace JIRA] Updated: (DS-768) All XMLUI Error Pages respond with 200 OK, instead of 404 Not Found

[Tim Donohue (DuraSpace JIRA)]

 [ 
https://jira.duraspace.org/browse/DS-768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tim Donohue updated DS-768:
---

  Description: 
In DSpace 1.7.0 RC1, the XMLUI "Page Not Found" page responds with a 200 OK, 
rather than the necessary 404 Not Found error.

For example:
http://demo.dspace.org/xmlui/NOTAVALIDPATH

I believe this used to function properly in 1.6.x, but it seems to be broken 
now.

Obviously, we want this to return a 404 Not Found, in order to ensure that 
search engines do not index "Page Not Found" responses.

Furthermore, it has been discovered that all other XMLUI Error pages (Cocoon 
Errors or Invalid Continuation errors) also respond with 200 OK.  In addition, 
it seems this affects all 1.6.x versions of DSpace, as the same responses can 
be found on http://dspace.mit.edu (currently running 1.6.0 with patches), and 
http://researchspace.auckland.ac.nz (currently running 1.6.2 with patches).

  was:
In DSpace 1.7.0 RC1, the XMLUI "Page Not Found" page responds with a 200 OK, 
rather than the necessary 404 Not Found error.

For example:
http://demo.dspace.org/xmlui/NOTAVALIDPATH

I believe this used to function properly in 1.6.x, but it seems to be broken 
now.

Obviously, we want this to return a 404 Not Found, in order to ensure that 
search engines do not index "Page Not Found" responses.

Affects Version/s: 1.6.0
   1.6.1
   1.6.2
  Summary: All XMLUI Error Pages respond with 200 OK, instead of 
404 Not Found  (was: 1.7.0 XMLUI "Page Not Found" returns a 200 OK, instead of 
404 Not Found)

Changed title and description above to detail that this invalid 200 OK response 
seems to affect all 1.6.x versions of DSpace, and is returned for *all* errors 
reported by XMLUI.

> All XMLUI Error Pages respond with 200 OK, instead of 404 Not Found
> ---
>
> Key: DS-768
> URL: https://jira.duraspace.org/browse/DS-768
> Project: DSpace
>  Issue Type: Bug
>  Components: XMLUI
>Affects Versions: 1.6.0, 1.6.1, 1.6.2, 1.7.0
>Reporter: Tim Donohue
>Priority: Major
> Fix For: 1.7.0
>
>
> In DSpace 1.7.0 RC1, the XMLUI "Page Not Found" page responds with a 200 OK, 
> rather than the necessary 404 Not Found error.
> For example:
> http://demo.dspace.org/xmlui/NOTAVALIDPATH
> I believe this used to function properly in 1.6.x, but it seems to be broken 
> now.
> Obviously, we want this to return a 404 Not Found, in order to ensure that 
> search engines do not index "Page Not Found" responses.
> Furthermore, it has been discovered that all other XMLUI Error pages (Cocoon 
> Errors or Invalid Continuation errors) also respond with 200 OK.  In 
> addition, it seems this affects all 1.6.x versions of DSpace, as the same 
> responses can be found on http://dspace.mit.edu (currently running 1.6.0 with 
> patches), and http://researchspace.auckland.ac.nz (currently running 1.6.2 
> with patches).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel

[Dspace-devel] [DuraSpace JIRA] Commented: (DS-768) 1.7.0 XMLUI "Page Not Found" returns a 200 OK, instead of 404 Not Found

[Tim Donohue (DuraSpace JIRA)]

[ 
https://jira.duraspace.org/browse/DS-768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18239#action_18239
 ] 

Tim Donohue commented on DS-768:


This problem also seems to extend to all error screens in 1.7.0 XMLUI.  
Currently the "Invalid Continuation" error screen (e.g. see DS-613), and 
general Cocoon Error screens both also return 200 OK instead of 404 Not Found.

I'm not sure what could have changed, as the error handling at the bottom of 
the main sitemap.xmap, specifically says to return a 404 response (see the 
'status-code' value below):

http://scm.dspace.org/svn/repo/dspace/trunk/dspace-xmlui/dspace-xmlui-webapp/src/main/webapp/sitemap.xmap

   








If anyone has an ideas on this, I'd appreciate suggestions.  I'll keep digging 
around a bit to see what I can figure out.


> 1.7.0 XMLUI "Page Not Found" returns a 200 OK, instead of 404 Not Found
> ---
>
> Key: DS-768
> URL: https://jira.duraspace.org/browse/DS-768
> Project: DSpace
>  Issue Type: Bug
>  Components: XMLUI
>Affects Versions: 1.7.0
>Reporter: Tim Donohue
>Priority: Major
> Fix For: 1.7.0
>
>
> In DSpace 1.7.0 RC1, the XMLUI "Page Not Found" page responds with a 200 OK, 
> rather than the necessary 404 Not Found error.
> For example:
> http://demo.dspace.org/xmlui/NOTAVALIDPATH
> I believe this used to function properly in 1.6.x, but it seems to be broken 
> now.
> Obviously, we want this to return a 404 Not Found, in order to ensure that 
> search engines do not index "Page Not Found" responses.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel

[Dspace-devel] [DuraSpace JIRA] Assigned: (DS-605) Blank screen on XMLUI Dspace 1.6.0

[Tim Donohue (DuraSpace JIRA)]

 [ 
https://jira.duraspace.org/browse/DS-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tim Donohue reassigned DS-605:
--

Assignee: Sands Fish

Sands,

Did this ever get resolved in the latest 1.7.0 code?

Do we need to do more testing against demo.dspace.org (or similar)?

Just wanted to check on status, as I know this was/is a big issue for some in 
1.6.0 XMLUI, and it'd be good to finally resolve for 1.7.0 XMLUI.

- Tim

> Blank screen on XMLUI Dspace 1.6.0
> --
>
> Key: DS-605
> URL: https://jira.duraspace.org/browse/DS-605
> Project: DSpace
>  Issue Type: Bug
>  Components: XMLUI
>Affects Versions: 1.6.0
> Environment: apache-tomcat-6.0.18
> jdk1.6.0_13
> Debian GNU Linux 5.0
>Reporter: Antero Neto
>Assignee: Sands Fish
>Priority: Critical
> Fix For: 1.7.0
>
>
> The interface of Dspce XMLUI shows a blank screen and I need to reboot Tomcat.
> JSPUI The interface is not affected by the issue. It happens sporadically. 
> I'm using version 1.6.0 of DSpace. I use a theme based on the theme 
> "Reference" which comes in DSpace.
> Below, some log information that may be related.
> 2010-06-09 00:07:00,741 ERROR cocoon.handled  - Could not read resource 
> cocoon://DRI/2/handle//xxx/workflow
> at  - 
> resource://aspects/Statistics/sitemap.xmap:70:31
> at  - 
> resource://aspects/Statistics/sitemap.xmap:38:55
> at  - resource://aspects/Statistics/sitemap.xmap:33:19
> ...
> org.apache.cocoon.ProcessingException: Could not read resource 
> cocoon://DRI/2/handle//xxx/workflow
> at  - 
> resource://aspects/Statistics/sitemap.xmap:70:31
> at  - 
> resource://aspects/Statistics/sitemap.xmap:38:55
> at  - resource://aspects/Statistics/sitemap.xmap:33:19
> ...
> Caused by: java.lang.NullPointerException
> at 
> org.apache.cocoon.components.source.impl.SitemapSource.init(SitemapSource.java:292)
> at 
> org.apache.cocoon.components.source.impl.SitemapSource.(SitemapSource.java:148)
> at 
> org.apache.cocoon.components.source.impl.SitemapSourceFactory.getSource(SitemapSourceFactory.java:62)
> at 
> org.apache.cocoon.components.source.CocoonSourceResolver.resolveURI(CocoonSourceResolver.java:153)
> at 
> org.apache.cocoon.components.source.CocoonSourceResolver.resolveURI(CocoonSourceResolver.java:183)
> at 
> org.apache.cocoon.generation.FileGenerator.setup(FileGenerator.java:99)
> at 
> org.dspace.app.xmlui.cocoon.AspectGenerator.setup(AspectGenerator.java:112)
> at sun.reflect.GeneratedMethodAccessor57.invoke(Unknown Source)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel

[Dspace-devel] [DuraSpace JIRA] Created: (DS-768) 1.7.0 XMLUI "Page Not Found" returns a 200 OK, instead of 404 Not Found

[Tim Donohue (DuraSpace JIRA)]

1.7.0 XMLUI "Page Not Found" returns a 200 OK, instead of 404 Not Found
---

 Key: DS-768
 URL: https://jira.duraspace.org/browse/DS-768
 Project: DSpace
  Issue Type: Bug
  Components: XMLUI
Affects Versions: 1.7.0
Reporter: Tim Donohue
Priority: Major
 Fix For: 1.7.0


In DSpace 1.7.0 RC1, the XMLUI "Page Not Found" page responds with a 200 OK, 
rather than the necessary 404 Not Found error.

For example:
http://demo.dspace.org/xmlui/NOTAVALIDPATH

I believe this used to function properly in 1.6.x, but it seems to be broken 
now.

Obviously, we want this to return a 404 Not Found, in order to ensure that 
search engines do not index "Page Not Found" responses.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel

[Dspace-devel] [DuraSpace JIRA] Resolved: (DS-396) Provide metatags used by Google Scholar for enhanced indexing

[Sands Fish (DuraSpace JIRA)]

 [ 
https://jira.duraspace.org/browse/DS-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sands Fish resolved DS-396.
---

Documentation Status: Complete or Committed  (was: Needed)
  Resolution: Fixed

Mapping and default configuration completed.  Any additional feedback on 
default mappings (in config/crosswalks/google-metadata.properties) from 
community would be valuable.

> Provide metatags used by Google Scholar for enhanced indexing
> -
>
> Key: DS-396
> URL: https://jira.duraspace.org/browse/DS-396
> Project: DSpace
>  Issue Type: New Feature
>Reporter: Sarah Shreeves
>Assignee: Sands Fish
>Priority: Major
> Fix For: 1.7.0
>
> Attachments: google-scholar-impl-quickndirty.patch, 
> google_scholar_for_dri_alt_and_mirage.patch
>
>
> In August 2009 I posted a query to the DSpace general list about whether or 
> not anyone else had seen strange indexing of items in DSpace (see 
> http://mailman.mit.edu/pipermail/dspace-general/2009-August/002996.html) and 
> MacKenzie Smith posted a follow up that stated she had seen the same things 
> (http://mailman.mit.edu/pipermail/dspace-general/2009-August/002998.html). 
> MacKenzie followed up with Anurag Acharya at Google Scholar to inquire about 
> this and he indicated that better support for the Google metatags schema 
> would help mitigate this problem. It looks like the metatags are (though we'd 
> want to confirm this with the Google Scholar team).
> 
> 
> 
> 
> 
> 
> 
> 
> 
>  content="http://www.publishername.org/10/1/1.pdf";>
>  content="http://www.publishername.org/cgi/content/abstract/10/1/1";>
>  content="http://www.publishername.org/cgi/content/full/10/1/1";> 
> 
> 
> 
> 
> 
>  I realize that supporting this level of granularity puts pressure on how we 
> structure metadata but I believe as a repository manager that it's critical 
> that we get this kind of support for Google Scholar into DSpace out of the 
> box - and hopefully will help minimize the problems that IDEALS has seen.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel

[Dspace-devel] Wrap up jira tickets for 1.7.0

[Peter Dietz]

Hi All,

Work for DSpace 1.7 is in bug-fix only mode, so this means that features
that have been added have had time to be tested. So you need to update
tickets assigned to you and update the status.
Basically, I'd like us to resolve all of our issues. We're past feature
freeze, so un-commited new features are postponed for the next release 1.8,
there is a jira version for 1.8.

Take a look at:

   - 1.7 
issuespage
   - 1.7 "To 
Do"page


 [image: 
Open]
Open
39
   23% [image: In
Progress]
In
Progress
1
   1% [image: 
Reopened]
Reopened
2
   1% [image: 
Resolved]
Resolved
111
   65% [image: 
Closed]
Closed
17
   10% [image: 
Received]
Received
2
   1%



Another issue is for all the issues sitting in 1.7 but are unassigned. I'm
not sure how to address those issues, other than just post-poning them for
the next version. Mea culpa for not assigning them.

Additionally, any bugs that crop-up during testing will need to be
resolved.


--
Peter Dietz
Systems Developer/Engineer
Ohio State University Libraries
--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel

[Dspace-devel] [DuraSpace JIRA] Resolved: (DS-522) Script to convert Apache accesslog data into solr stats records

[Peter Dietz (DuraSpace JIRA)]

 [ 
https://jira.duraspace.org/browse/DS-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Peter Dietz resolved DS-522.


   Resolution: Won't Fix
Fix Version/s: (was: 1.7.0)

I'm not sure if there is much interest in this feature, and I no longer need 
the functionality, so I'm closing this as Won't Fix. 

> Script to convert Apache accesslog data into solr stats records
> ---
>
> Key: DS-522
> URL: https://jira.duraspace.org/browse/DS-522
> Project: DSpace
>  Issue Type: New Feature
>  Components: Solr
>Affects Versions: 1.6.0, 1.6.1
>Reporter: Peter Dietz
>Assignee: Peter Dietz
> Attachments: DS-ApacheLogConverter-1.patch, 
> DS-ApacheLogConverter-1b.patch
>
>
> Patch added that allows Apache's access log data to be used to possible 
> supplant dspace.log data.
> Before running clean up your access log with an awk command.
> awk '{print $4,$5,",",$7,",","DB",",","anonymous",",",$1}' 
> /path/to/access_log > /path/out/access_log_intermediate
> Then this command can be invoked with dspace.
> [dspace/bin/] ./dspace stats-apachelog-converter -i 
> /path/out/access_log_intermediate -o /path/solr/solrready
> Currently, it skips "/dspace/retrieve/40199/1990-RA-01.jpg.jpg" entries.
> Check it out, and helpful find some bugs in it for me to fix. The rationale 
> for wanting to add this is because our dspace.log files got rolled over into 
> dspace.log.0 -- dspace.log.500, thus we have some missing data that this 
> converter could fill the void for.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira



--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel

[Dspace-devel] [DuraSpace JIRA] Created: (DS-767) OAI-PMH verb ListIdentifiers deleted status in header

[DuraSpace JIRA]

OAI-PMH verb ListIdentifiers deleted status in header
-

 Key: DS-767
 URL: https://jira.duraspace.org/browse/DS-767
 Project: DSpace
  Issue Type: Improvement
  Components: DSpace API
Affects Versions: 1.6.2, 1.6.1, 1.6.0, 1.5.2, 1.5.1, 1.5.0
Reporter: Claudia Jürgen


In the DSpace OAI implementation the ListRecords and ListIdentifiers creation 
of headers varies. ListRecords does include the deleted status whereas 
ListIdentifiers does not. For ListIdentifiers the status is optional see 
http://www.openarchives.org/OAI/openarchivesprotocol.html#ListIdentifiers, but 
as DSpace per default sets the deleted status to persistent, the header should 
include the status.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://jira.duraspace.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

   

--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel

[Dspace-devel] DS-755 needs reviewed

[TAYLOR Robin]

Hi all,

If anyone has a chance could they cast a quick eye over...

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

Its definitely a bug and its one that would be good to fix in 1.7. I would 
appreciate it if someone could have a quick look at the patch or attached class 
to see if I have made any obvious blunders. All I have done is added a 'try, 
finally' to the generate() method.

Thanks, Robin.


Robin Taylor
Main Library
University of Edinburgh
Tel. 0131 6513808 
-- 
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.


--
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
___
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel