[dspace-tech] Re: DOI Error Message

[Oliver Goldschmidt]

Dear Richard,

sorry for being unclear. My idea was, that your problem had something to do 
with the item you wanted to register/reserve or update at DataCite. But 
your logfile snippets do not fit into this idea, so I guess I was wrong 
with that...

Anyway, what I was proposing was to look into the XML data, that is being 
sent to DataCite. You can see the XML output with the DSpace Command Line 
Tool by typing

[dspace-dir]/bin/dspace dsrun 
org.dspace.content.crosswalk.XSLTDisseminationCrosswalk DataCite 
In order to have that working you need the handle of the items (the DOI is 
not enough).

For toubleshooting it might be helpful to see the output of your doi 
organiser. You can see what the doi-organiser will do, when you use the 
same command line tool, too:

[dspace-dir]/bin/dspace doi-organiser -l

This command should show you, what the doi-organiser will do and you can 
use the dsrun command to see, what XML data will be sent to DataCite when 
you execute the doi-organiser for reservation with [dspace-dir]/bin/dspace 
doi-organiser -r (I guess this is the point where you get the error, isn't 
it?).

Is my troubleshooting approach clearer now?

Best
Oliver

Am Dienstag, 21. April 2020 00:14:16 UTC+2 schrieb Richard Dennis:
>
> Dear Oliver,
>
> I am not sure what you mean and I am not sure what you mean can you 
> explain in greater detail what you mean and what I should change the handle 
> with.
> I am totally lost at this point in this troubleshooting of DOI
>
> Regards,
>
> Richard
>
> On Monday, April 20, 2020 at 8:57:04 AM UTC+2, Oliver Goldschmidt wrote:
>>
>> Hello Richard,
>>
>> I think I have seen this error in a context, where you try to send 
>> invalid XML to DataCite. This is specific to the item you want to 
>> register/reserve/update. You can see the XML output, which is sent to 
>> DataCite with this command:
>>
>> ./bin/dspace dsrun 
>> org.dspace.content.crosswalk.XSLTDisseminationCrosswalk DataCite 
>>
>> Just replace  with the handle of your item (I'm not sure, if this 
>> will work with an internal ID, though). This might help to find the issue 
>> with your record...
>>
>> Best 
>> Oliver
>>
>> Am Samstag, 11. April 2020 23:15:37 UTC+2 schrieb Richard Dennis:
>>>
>>> Hello All,
>>>
>>> Running DSpace 6.2
>>> Linux Ubuntu 16.04
>>> Oracle DB
>>>
>>> I get this error message the following error  Date:4/11/20 8:00 PM
>>>
>>>  
>>>
>>> Update DOI doi:10.22006/dspacebeta-84 for ITEM with ID 
>>> 99c212b0-c1aa-4fa1-925a-c1d800d5a07a failed:
>>>
>>> BAD_ANSWER
>>>
>>>
>>> Can anyone out there assist me with this error message.
>>>
>>>
>>> Is it in my dspace.cfg ?
>>>
>>> According to Data Cite all is ok at their end.
>>>
>>>
>>> what should I do?
>>>
>>>
>>> Many thanks in advance
>>>
>>>
>>>
>>> Richard Dennis
>>>
>>> University Library of Southern Denmark
>>>
>>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/a0eb1ecc-ebdf-4ab7-932b-e04d8831462e%40googlegroups.com.

Re: [dspace-tech] DSpace 7.0 Beta1 Release - Unable to 'Create a new top-level community'

[Eric Montague]

I tried beta2, and the problem is fixed.


Thanks.


-eric


On 4/21/2020 1:42 PM, Eric Montague wrote:


Thanks Tim,


I saw the beta2 announcement. I'll check it out.


- eric


On 4/21/2020 1:29 PM, Tim Donohue wrote:

Hi Eric,

The problems you ran into were caused by an undiscovered bug in that 
beta1 release that we fixed a few weeks ago (see: 
https://github.com/DSpace/dspace-angular/pull/640)


This should now work in the beta2 release (see the recent email 
announcing that release).


Tim

*From:* dspace-tech@googlegroups.com  
on behalf of Eric Montague 

*Sent:* Monday, April 20, 2020 2:11 PM
*To:* DSpace Technical Support 
*Subject:* [dspace-tech] DSpace 7.0 Beta1 Release - Unable to 'Create 
a new top-level community'

I have installed both dspace-angular-dspace-7.0-beta1 (front end)
and DSpace-dspace-7.0-beta1 (back end) locally on Windows 10.

When I attempt to 'Create a new top-level community', I see the
following in the Firefox browser console,
and the pages shows 'Loading ...' beneath the page header.

Error:
{…}
​error: {…}
​​error: "Not Found"
​​message: "An Exception has occured"
​​path: "/server/api/core/communities/create"
​​status: 404
​timestamp: "2020-04-20T18:37:27.274+"
​​trace:
"org.springframework.data.rest.webmvc.ResourceNotFoundException:
core.communities with id: create not found at
org.dspace.app.rest.RestResourceController.findOneInternal(RestResourceController.java:230) 


at
org.dspace.app.rest.RestResourceController.findOne(RestResourceController.java:188) 


at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
Method) at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 


at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 


at java.base/java.lang.reflect.Method.invoke(Method.java:566) at
org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:190) 


at
org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:138) 


at
org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocable…"
​​
: Object { … }
​headers: Object { normalizedNames: Map(0), lazyUpdate: null, lazyInit:
lazyInit() }
​message: "Http failure response for
http://localhost:8080/server/api/core/communities/create: 404 OK"
​name: "HttpErrorResponse"
​ok: false
​status: 404
​statusText: "OK"
​
url: "http://localhost:8080/server/api/core/communities/create";
​: Object { constructor: HttpErrorResponse(init) }
dspace-rest-v2.service.ts:105:16
Object { statusCode: 404, statusText: "OK", message: "Http failure
response for http://localhost:8080/server/api/core/communities/create:
404 OK" }
response.models.ts:186:12

--
All messages to this mailing list should adhere to the DuraSpace Code 
of Conduct: https://duraspace.org/about/policies/code-of-conduct/

---
You received this message because you are subscribed to the Google 
Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, 
send an email to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/85febb39-7b2d-bf26-c6a6-72e77cdf02e9%40comcast.net.

--
All messages to this mailing list should adhere to the DuraSpace Code 
of Conduct: https://duraspace.org/about/policies/code-of-conduct/

---
You received this message because you are subscribed to the Google 
Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, 
send an email to dspace-tech+unsubscr...@googlegroups.com 
.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/DM5PR2201MB11486223E41AB04FBBEC6FE8EDD50%40DM5PR2201MB1148.namprd22.prod.outlook.com 
.


--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/f2150dd2-2c35-25f6-dffc-96baedc90f69%40comcast.net.

Re: [dspace-tech] DSpace 7.0 Beta1 Release - Unable to 'Create a new top-level community'

[Eric Montague]

Thanks Tim,


I saw the beta2 announcement. I'll check it out.


- eric


On 4/21/2020 1:29 PM, Tim Donohue wrote:

Hi Eric,

The problems you ran into were caused by an undiscovered bug in that 
beta1 release that we fixed a few weeks ago (see: 
https://github.com/DSpace/dspace-angular/pull/640)


This should now work in the beta2 release (see the recent email 
announcing that release).


Tim

*From:* dspace-tech@googlegroups.com  on 
behalf of Eric Montague 

*Sent:* Monday, April 20, 2020 2:11 PM
*To:* DSpace Technical Support 
*Subject:* [dspace-tech] DSpace 7.0 Beta1 Release - Unable to 'Create 
a new top-level community'

I have installed both dspace-angular-dspace-7.0-beta1 (front end)
and DSpace-dspace-7.0-beta1 (back end) locally on Windows 10.

When I attempt to 'Create a new top-level community', I see the
following in the Firefox browser console,
and the pages shows 'Loading ...' beneath the page header.

Error:
{…}
​error: {…}
​​error: "Not Found"
​​message: "An Exception has occured"
​​path: "/server/api/core/communities/create"
​​status: 404
​timestamp: "2020-04-20T18:37:27.274+"
​​trace:
"org.springframework.data.rest.webmvc.ResourceNotFoundException:
core.communities with id: create not found at
org.dspace.app.rest.RestResourceController.findOneInternal(RestResourceController.java:230) 


at
org.dspace.app.rest.RestResourceController.findOne(RestResourceController.java:188) 


at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
Method) at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 


at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 


at java.base/java.lang.reflect.Method.invoke(Method.java:566) at
org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:190) 


at
org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:138) 


at
org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocable…"
​​
: Object { … }
​headers: Object { normalizedNames: Map(0), lazyUpdate: null, lazyInit:
lazyInit() }
​message: "Http failure response for
http://localhost:8080/server/api/core/communities/create: 404 OK"
​name: "HttpErrorResponse"
​ok: false
​status: 404
​statusText: "OK"
​
url: "http://localhost:8080/server/api/core/communities/create";
​: Object { constructor: HttpErrorResponse(init) }
dspace-rest-v2.service.ts:105:16
Object { statusCode: 404, statusText: "OK", message: "Http failure
response for http://localhost:8080/server/api/core/communities/create:
404 OK" }
response.models.ts:186:12

--
All messages to this mailing list should adhere to the DuraSpace Code 
of Conduct: https://duraspace.org/about/policies/code-of-conduct/

---
You received this message because you are subscribed to the Google 
Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/85febb39-7b2d-bf26-c6a6-72e77cdf02e9%40comcast.net.

--
All messages to this mailing list should adhere to the DuraSpace Code 
of Conduct: https://duraspace.org/about/policies/code-of-conduct/

---
You received this message because you are subscribed to the Google 
Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send 
an email to dspace-tech+unsubscr...@googlegroups.com 
.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/DM5PR2201MB11486223E41AB04FBBEC6FE8EDD50%40DM5PR2201MB1148.namprd22.prod.outlook.com 
.


--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/f402906b-a29b-dc2f-0a20-af75e72b30a0%40comcast.net.

Re: [dspace-tech] DSpace 7.0 Beta1 Release - Unable to 'Create a new top-level community'

[Tim Donohue]

Hi Eric,

The problems you ran into were caused by an undiscovered bug in that beta1 
release that we fixed a few weeks ago (see: 
https://github.com/DSpace/dspace-angular/pull/640)

This should now work in the beta2 release (see the recent email announcing that 
release).

Tim

From: dspace-tech@googlegroups.com  on behalf of 
Eric Montague 
Sent: Monday, April 20, 2020 2:11 PM
To: DSpace Technical Support 
Subject: [dspace-tech] DSpace 7.0 Beta1 Release - Unable to 'Create a new 
top-level community'

I have installed both dspace-angular-dspace-7.0-beta1 (front end)
and DSpace-dspace-7.0-beta1 (back end) locally on Windows 10.

When I attempt to 'Create a new top-level community', I see the
following in the Firefox browser console,
and the pages shows 'Loading ...' beneath the page header.

Error:
{…}
​error: {…}
​​error: "Not Found"
​​message: "An Exception has occured"
​​path: "/server/api/core/communities/create"
​​status: 404
​timestamp: "2020-04-20T18:37:27.274+"
​​trace:
"org.springframework.data.rest.webmvc.ResourceNotFoundException:
core.communities with id: create not found at
org.dspace.app.rest.RestResourceController.findOneInternal(RestResourceController.java:230)
at
org.dspace.app.rest.RestResourceController.findOne(RestResourceController.java:188)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
Method) at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566) at
org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:190)
at
org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:138)
at
org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocable…"
​​
: Object { … }
​headers: Object { normalizedNames: Map(0), lazyUpdate: null, lazyInit:
lazyInit() }
​message: "Http failure response for
http://localhost:8080/server/api/core/communities/create: 404 OK"
​name: "HttpErrorResponse"
​ok: false
​status: 404
​statusText: "OK"
​
url: "http://localhost:8080/server/api/core/communities/create";
​: Object { constructor: HttpErrorResponse(init) }
dspace-rest-v2.service.ts:105:16
Object { statusCode: 404, statusText: "OK", message: "Http failure
response for http://localhost:8080/server/api/core/communities/create:
404 OK" }
response.models.ts:186:12

--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/85febb39-7b2d-bf26-c6a6-72e77cdf02e9%40comcast.net.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/DM5PR2201MB11486223E41AB04FBBEC6FE8EDD50%40DM5PR2201MB1148.namprd22.prod.outlook.com.

Re: [dspace-tech] DOI Error Message

[Richard Dennis]

Dear Paul,

My apologies for sending you the full log file,

Please find below a snippet of the error message in the dspace.log file

".
2020-04-19 04:00:38,839 ERROR org.dspace.identifier.doi.DOIOrganiser @ It 
wasn't possible to update this identifier:  doi:10.22006/dspacebeta-84 
Exceptions code:  BAD_ANSWER
org.dspace.identifier.doi.DOIIdentifierException: Unable to parse an answer 
from DataCite API. Please have a look into DSpace logs.
at 
org.dspace.identifier.doi.DataCiteConnector.reserveDOI(DataCiteConnector.java:500)
at 
org.dspace.identifier.doi.DataCiteConnector.updateMetadata(DataCiteConnector.java:582)
at 
org.dspace.identifier.DOIIdentifierProvider.updateMetadataOnline(DOIIdentifierProvider.java:420)
at org.dspace.identifier.doi.DOIOrganiser.update(DOIOrganiser.java:594)
at org.dspace.identifier.doi.DOIOrganiser.runCLI(DOIOrganiser.java:240)
at org.dspace.identifier.doi.DOIOrganiser.main(DOIOrganiser.java:71)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:229)
at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:81)
2020-04-19 04:00:39,138 WARN  org.dspace.identifier.doi.DataCiteConnector @ 
While reserving the DOI doi:10.22006/dspacebeta-124, we got a http status 
code 404 and the message "



Error


Cannot POST /metadata/


".
2020-04-19 04:00:39,153 ERROR org.dspace.identifier.doi.DOIOrganiser @ It 
wasn't possible to update this identifier:  doi:10.22006/dspacebeta-124 
Exceptions code:  BAD_ANSWER
org.dspace.identifier.doi.DOIIdentifierException: Unable to parse an answer 
from DataCite API. Please have a look into DSpace logs.
at 
org.dspace.identifier.doi.DataCiteConnector.reserveDOI(DataCiteConnector.java:500)
at 
org.dspace.identifier.doi.DataCiteConnector.updateMetadata(DataCiteConnector.java:582)
at 
org.dspace.identifier.DOIIdentifierProvider.updateMetadataOnline(DOIIdentifierProvider.java:420)
at org.dspace.identifier.doi.DOIOrganiser.update(DOIOrganiser.java:594)
at org.dspace.identifier.doi.DOIOrganiser.runCLI(DOIOrganiser.java:240)
at org.dspace.identifier.doi.DOIOrganiser.main(DOIOrganiser.java:71)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:229)
at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:81)
2020-04-19 04:00:39,420 WARN  org.dspace.identifier.doi.DataCiteConnector @ 
While reserving the DOI doi:10.22006/dspacebeta-81, we got a http status 
code 404 and the message "



Error


Cannot POST /metadata/


".
2020-04-19 04:00:39,435 ERROR org.dspace.identifier.doi.DOIOrganiser @ It 
wasn't possible to update this identifier:  doi:10.22006/dspacebeta-81 
Exceptions code:  BAD_ANSWER
org.dspace.identifier.doi.DOIIdentifierException: Unable to parse an answer 
from DataCite API. Please have a look into DSpace logs.
at 
org.dspace.identifier.doi.DataCiteConnector.reserveDOI(DataCiteConnector.java:500)
at 
org.dspace.identifier.doi.DataCiteConnector.updateMetadata(DataCiteConnector.java:582)
at 
org.dspace.identifier.DOIIdentifierProvider.updateMetadataOnline(DOIIdentifierProvider.java:420)
at org.dspace.identifier.doi.DOIOrganiser.update(DOIOrganiser.java:594)
at org.dspace.identifier.doi.DOIOrganiser.runCLI(DOIOrganiser.java:240)
at org.dspace.identifier.doi.DOIOrganiser.main(DOIOrganiser.java:71)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:229)
at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:81)
2020-04-19 04:00:39,716 WARN  org.dspace.identifier.doi.DataCiteConnector @ 
While reserving the DOI doi:10.22006/dspacebeta-82, we got a http status 
code 404 and the message "



Error


Cannot POST /metadata/



thank 

Richard



On Monday, April 20, 2020 at 8:41:14 AM UTC+2, Paul Münch wrote:
>
> Dear Richard, 
>
> could you please copy the specific log message. I don’t want to read your 
> whole log file by myself. And maybe there are some privacy issues that I 
> don’t want to have anything to do with. 
>
> Kind regards, 
>
> Paul Münch 
>
>
> > Am 20.04.2020 um 00:49 schrieb Richard Dennis  >: 
> > 
> > Dear Paul, 
> > 
> > See attached the log file as requested. 
> > 
> > Regards, 
> >

Re: [dspace-tech] making private during itemimport

[Tim Donohue]

Hi Jose,

Yes, that's possible. There are two types of Embargo in DSpace.  You can 
Embargo *just* the Bitstream, which would mean that the Item is still 
searchable/browsable, but the Bitstream is not downloadable.  Or you can 
Embargo the entire *Item* (which sounds like what you want), in which case the 
entire Item is not accessible/searchable/browsable until the Embargo expires.

To Embargo the entire *Item* you need to have the "AccessStep" enabled in the 
Submission process, and specify the "Embargo Access until Specific Date"  See 
https://wiki.lyrasis.org/display/DSDOC6x/Embargo#Embargo-SimpleEmbargoSettings

If you only wanted to Embargo the bitstream, you'd instead use the 
"UploadWithEmbargoStep".  You can choose to enable either of these steps 
individually or both, depending on the type(s) of embargo you'd like to allow.

When doing a Batch import, you should be able to initialize/create an 
Item-Level Embargo via metadata (however, you cannot update an existing embargo 
in this way, that would need to be done via the UI or similar).  See the docs 
at: 
https://wiki.lyrasis.org/display/DSDOC6x/Embargo#Embargo-CreatingEmbargoesviaMetadata

Tim


From: dspace-tech@googlegroups.com  on behalf of 
Jose Blanco 
Sent: Tuesday, April 21, 2020 10:41 AM
To: Tim Donohue 
Cc: DSpace Technical Support 
Subject: Re: [dspace-tech] making private during itemimport

Tim, I was thinking of the private that means items never show up via search or 
browse.  We're thinking of using the Embago that comes with 63, and in the 
process of marking something as embargoed, you can set it to private also when 
using the via ( not sure I can do this using itemimport? ). I was assuming that 
when the embargo is lifted the private status is removed.  But perhaps it's 
not.  The bottom line is that we don't want embargoed items to show up in 
search or browser until the embargo expires. Possible?

-Jose

On Tue, Apr 21, 2020 at 10:55 AM Tim Donohue 
mailto:tim.dono...@lyrasis.org>> wrote:
Hi Jose,

I'm assuming by "private" you just mean access restricted?  Please be aware 
that the term "private" can mean two different things in DSpace.  There's the 
"private item flag" which doesn't access restrict an item...it just hides it so 
that it's only available via a direct link/bookmark, see  
https://wiki.lyrasis.org/display/DSDOC6x/DSpace+Item+State+Definitions

There's also the capability to access restrict an entire item (so metadata + 
files cannot be visible without special permissions), or just the bitstreams 
(so that metadata is publicly visible but bitstreams are *not* visible or 
downloadable).

Using the Item Import script, at this time it's only possible to access 
restrict *bitstreams* via the "contents" file. See description of the 
"contents" file in this section of the docs: 
https://wiki.lyrasis.org/display/DSDOC6x/Importing+and+Exporting+Items+via+Simple+Archive+Format#ImportingandExportingItemsviaSimpleArchiveFormat-DSpaceSimpleArchiveFormat

However, if you want all Items deposited to a Collection to be automatically 
access restricted (at the Item level), you can change the Collection's "Default 
read access" setting/group (in the Edit Collection screen).  If you change that 
setting, then all Items submitted into the Collection will automatically be 
access restricted to that Group.

Tim

From: dspace-tech@googlegroups.com 
mailto:dspace-tech@googlegroups.com>> on behalf 
of Jose Blanco mailto:blan...@umich.edu>>
Sent: Tuesday, April 21, 2020 8:43 AM
To: DSpace Technical Support 
mailto:dspace-tech@googlegroups.com>>
Subject: [dspace-tech] making private during itemimport

Is there a way to make an item private when using the itemimport script in 6.3. 
 I could not find documentation on that.

Thank you!
-Jose

--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CAK%3DKc-t-RyvHnXspJTkUkjMVgvMp1pw9pP44C5v5X65A%3DATgtA%40mail.gmail.com.

--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegr

[dspace-tech] NOW AVAILABLE: DSpace 7.0 Beta 2

[tim.donohue]

Dear DSpace Community,


The DSpace Leadership Group, the DSpace Committers and LYRASIS are proud to 
announce that DSpace 7.0 Beta 2 is now available for download and testing.


Beta 2 is the second scheduled Beta release provided for community feedback and 
to introduce the new features of the 7.0 platform. As a Beta release, we highly 
advise against running this version in production. Rather, we ask that you 
consider installing it in a test environment, try it out, and report back any 
issues or bugs you notice through the JIRA issue 
tracker.


DSpace 7.0 Beta 2 is deployed for public testing on a dedicated demo site and 
it can be installed manually or via a Docker “quick install”.  Instructions are 
available at: Try out DSpace 
7.

Included in Beta 2


  *   Administrative Search (video) combines 
retrieval of withdrawn items and private items, together with a series of quick 
action buttons.

  *   EPeople, Groups and Roles can now be viewed, created and updated.

  *   Bitstream Editing (video) has a 
drag-and-drop interface for re-ordering bitstreams and makes adding and editing 
bitstreams more intuitive.

  *   Metadata Editing (video) introduces 
suggest-as-you-type for field name selection of new metadata.

  *   Shibboleth 
Authentication

  *   Viewing Item Version History

  *   Collection and Community (video) creation 
and edit pages.

  *   English, Latvian, Dutch, German, French, Portuguese and Spanish language 
catalogs

  *   Security and authorization improvements, including REST API support 
hiding specific metadata fields (metadata.hide property) and upgrades of 
different software packages on which DSpace 7 depends.

Source: DSpace 7 Release 
Notes

Coming soon


In the remainder of April, the contributors are focusing on a planning sprint 
to review the remaining release goals and (as necessary) adjust the 7.0 final 
release schedule.


  *   Beta 3: Beta release focusing on Account Profiles, Submission/Workflow 
enhancements, additional Administrative tools

  *   Beta 4: Beta release focusing on SEO enhancements, Theming enhancements, 
Batch processing tools, Solr-based Statistics views, improved GDPR alignment

  *   Beta 5: Optional Beta release to cleanup any bugs or issues found in 
previous Betas, or complete any incomplete features.

  *   7.0 Final Release: The final, production-ready release of 7.0 will be 
released as soon as all the above Betas have been completed and any outstanding 
major bugs have been resolved. Roughly estimated at 1-2 months after the last 
Beta.

More information and the latest changes can be found on DSpace 7 Release 
Goals.
Learn more


A number of recorded presentations and workshops are available through 
following links:


  *   Open Repository 2019 Hamburg Presentations & 
Workshops

  *   Getting Started with DSpace 7 Workshop - North American User Group 
Meeting


Initial preparations and edits are being made to the official documentation for 
DSpace 7.

Thanks to major code contributors!


The following organizations have been major code contributors to DSpace 7.


Atmire

4Science

FCT / RCAAP



We gratefully recognize the following institutions, who together have 
generously contributed financially to support the DSpace 7 staged release 
program:


Cornell University

Duke University

Imperial College London

Indiana University–Purdue University, Indianapolis

LYRASIS

National Library of Finland

The Ohio State University

Texas Digital Library

University of Arizona

University of Edinburgh

University of Kansas

University of Minnesota




--

Tim Donohue

Technical Lead, DSpace

tim.dono...@lyrasis.org

Lyrasis.org | DSpace.org

[cid:5301cbd2-248d-4a21-946c-9655403c12f6]

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/DM5PR2201MB11483183618552A9E6BB23B6EDD40%40DM5PR2201MB1148.namprd22.prod.outlook.com.

Re: [dspace-tech] making private during itemimport

[Jose Blanco]

Tim, I was thinking of the private that means items never show up via
search or browse.  We're thinking of using the Embago that comes with 63,
and in the process of marking something as embargoed, you can set it to
private also when using the via ( not sure I can do this using itemimport?
). I was assuming that when the embargo is lifted the private status is
removed.  But perhaps it's not.  The bottom line is that we don't want
embargoed items to show up in search or browser until the embargo expires.
Possible?

-Jose

On Tue, Apr 21, 2020 at 10:55 AM Tim Donohue 
wrote:

> Hi Jose,
>
> I'm assuming by "private" you just mean access restricted?  Please be
> aware that the term "private" can mean two different things in DSpace.
> There's the "private item flag" which doesn't access restrict an item...it
> just hides it so that it's only available via a direct link/bookmark, see
> https://wiki.lyrasis.org/display/DSDOC6x/DSpace+Item+State+Definitions
>
> There's also the capability to access restrict an entire item (so metadata
> + files cannot be visible without special permissions), or just the
> bitstreams (so that metadata is publicly visible but bitstreams are *not*
> visible or downloadable).
>
> Using the Item Import script, at this time it's only possible to access
> restrict *bitstreams* via the "contents" file. See description of the
> "contents" file in this section of the docs:
> https://wiki.lyrasis.org/display/DSDOC6x/Importing+and+Exporting+Items+via+Simple+Archive+Format#ImportingandExportingItemsviaSimpleArchiveFormat-DSpaceSimpleArchiveFormat
>
> However, if you want all Items deposited to a Collection to be
> automatically access restricted (at the Item level), you can change the
> Collection's "Default read access" setting/group (in the Edit Collection
> screen).  If you change that setting, then all Items submitted into the
> Collection will automatically be access restricted to that Group.
>
> Tim
> --
> *From:* dspace-tech@googlegroups.com  on
> behalf of Jose Blanco 
> *Sent:* Tuesday, April 21, 2020 8:43 AM
> *To:* DSpace Technical Support 
> *Subject:* [dspace-tech] making private during itemimport
>
> Is there a way to make an item private when using the itemimport script in
> 6.3.  I could not find documentation on that.
>
> Thank you!
> -Jose
>
> --
> All messages to this mailing list should adhere to the DuraSpace Code of
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> You received this message because you are subscribed to the Google Groups
> "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dspace-tech+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/dspace-tech/CAK%3DKc-t-RyvHnXspJTkUkjMVgvMp1pw9pP44C5v5X65A%3DATgtA%40mail.gmail.com
> 
> .
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CAK%3DKc-t9xcfW_9-%3DKPV-HBUkmjMVFXeEi-NXhNu96YMZP3DbeQ%40mail.gmail.com.

Re: [dspace-tech] making private during itemimport

[Tim Donohue]

Hi Jose,

I'm assuming by "private" you just mean access restricted?  Please be aware 
that the term "private" can mean two different things in DSpace.  There's the 
"private item flag" which doesn't access restrict an item...it just hides it so 
that it's only available via a direct link/bookmark, see  
https://wiki.lyrasis.org/display/DSDOC6x/DSpace+Item+State+Definitions

There's also the capability to access restrict an entire item (so metadata + 
files cannot be visible without special permissions), or just the bitstreams 
(so that metadata is publicly visible but bitstreams are *not* visible or 
downloadable).

Using the Item Import script, at this time it's only possible to access 
restrict *bitstreams* via the "contents" file. See description of the 
"contents" file in this section of the docs: 
https://wiki.lyrasis.org/display/DSDOC6x/Importing+and+Exporting+Items+via+Simple+Archive+Format#ImportingandExportingItemsviaSimpleArchiveFormat-DSpaceSimpleArchiveFormat

However, if you want all Items deposited to a Collection to be automatically 
access restricted (at the Item level), you can change the Collection's "Default 
read access" setting/group (in the Edit Collection screen).  If you change that 
setting, then all Items submitted into the Collection will automatically be 
access restricted to that Group.

Tim

From: dspace-tech@googlegroups.com  on behalf of 
Jose Blanco 
Sent: Tuesday, April 21, 2020 8:43 AM
To: DSpace Technical Support 
Subject: [dspace-tech] making private during itemimport

Is there a way to make an item private when using the itemimport script in 6.3. 
 I could not find documentation on that.

Thank you!
-Jose

--
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CAK%3DKc-t-RyvHnXspJTkUkjMVgvMp1pw9pP44C5v5X65A%3DATgtA%40mail.gmail.com.

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/DM5PR2201MB11486334193DE31536BC5C4AEDD50%40DM5PR2201MB1148.namprd22.prod.outlook.com.

Re: [dspace-tech] The term "legacy" in Statistics

[Jeffrey Sheldon]

Is DS-4066 not related?

https://jira.lyrasis.org/browse/DS-4066

This patch will be introduced with the 6.4 rollout despite much earlier target 
dates.

https://wiki.lyrasis.org/display/DSPACE/DSpace+6.4+Release+Status

There will be a new command for migrating pre-6.x statistics:

https://wiki.lyrasis.org/display/DSDOC6x/SOLR+Statistics+Maintenance#SOLRStatisticsMaintenance-UpgradeLegacyDSpaceObjectIdentifiers(pre-6xstatistics)toDSpace6xUUIDIdentifiers


-Jeff



From: dspace-tech@googlegroups.com  on behalf of 
Bram Luyten 
Sent: Tuesday, April 21, 2020 8:49 AM
To: George Kozak
Cc: DSpace Technical Support
Subject: Re: [dspace-tech] The term "legacy" in Statistics

Hi George,

I think stats are only shown for bitstreams that haven't been deleted.

As a test, I deleted a bitstream from an item in 
demo.dspace.org, that previously had download stats, 
and those are now totally gone from:
http://demo.dspace.org/xmlui/handle/10673/81/statistics

best regards,

Bram

[logo]  Bram Luyten
250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586
Gaston Geenslaan 14, 3001 Leuven, Belgium
DSpace Express 
Hosting
 - Open Repository 
Hosting
 - Custom DSpace 
Services


On Tue, 21 Apr 2020 at 14:23, George Kozak 
mailto:gkoz...@gmail.com>> wrote:
Thanks, again, Bram.
So, am I right in assuming that “legacy” can be applied to both deleted 
bitstreams and items affected by the switch to uuids in DSpace 6?
George

On Tue, Apr 21, 2020 at 2:15 AM Bram Luyten 
mailto:b...@atmire.com>> wrote:
Hi George,

Emilio Lorenzo from Arvo.es sent me an off-list reply that I may have got it 
wrong here.

It's likely that legacy refers to the legacy item-id system, with sequential 
ids (DSpace 5 and earlier), as opposed to the new uuid approach since DSpace 6.

This is discussed and documented here: https://jira.lyrasis.org/browse/DS-3602

I didn't look closely enough and was wrong in my initial reply. Thanks again 
Emilio for the correction !!!

cheers,

Bram

[logo]  Bram Luyten
250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 
14586
Gaston Geenslaan 14, 3001 Leuven, 
Belgium
DSpace Express 
Hosting
 - Open Repository 
Hosting
 - Custom DSpace 
Services


On Mon, 20 Apr 2020 at 20:20, George Kozak 
mailto:gkoz...@gmail.com>> wrote:
Thanks you, Bram!  This was very helpful.
George Kozak
Cornell University

On Mon, Apr 20, 2020 at 2:44 AM Bram Luyten 
mailto:b...@atmire.com>> wrote:
Hi George,

the (legacy) note is added here:
https://github.com/DSpace/DSpace/blob/820722d2e6e848a5b486c56b6596ce1473d16792/dspace-api/src/main/java/org/dspace/statistics/content/StatisticsDataVisits.java#L543

By skimming through the code, I think it means that these are usage events that 
are still present in SOLR, while the original bitstream has been deleted.

This seems to check out when looking at:
https://ecommons.cornell.edu/handle/1813/7642

The two public bitstreams have sequence IDs 4 and 6, meaning that you likely 
had additional bitstreams there, sequence id 1, 2, 3 and 5, and that those 
might be deleted?

hope this helps,

Bram

[logo]  Bram Luyten
250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 
14586
Gaston Geenslaan 14, 3001 Leuven, 
Belgium
DSpace Express 
Hosting
 - Open Repository 
Hosting
 - Custom DSpace 
Services


On Mon, 20 Apr 2020 at 00:22, George Kozak 
mailto:gkoz...@gmail.com>> wrote:
Hi,
We are using DSpace 6.3 (XMLUI).  An author pointed out to us that the "View 
Usage Statistics" (https://ecommons.cornell.edu/handle/1813/7642/statistics) 
for his book in our DSpace has 2 categories:
A ... 3549
A ...(legacy) 755

He asked what "legacy" means.  I wasn't sure, does someone

Re: [dspace-tech] The term "legacy" in Statistics

[Bram Luyten]

Hi George,

I think stats are only shown for bitstreams that haven't been deleted.

As a test, I deleted a bitstream from an item in demo.dspace.org, that
previously had download stats, and those are now totally gone from:
http://demo.dspace.org/xmlui/handle/10673/81/statistics

best regards,

Bram

[image: logo] Bram Luyten
250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586
Gaston Geenslaan 14, 3001 Leuven, Belgium
DSpace Express Hosting

 - Open Repository Hosting

 - Custom DSpace Services



On Tue, 21 Apr 2020 at 14:23, George Kozak  wrote:

> Thanks, again, Bram.
> So, am I right in assuming that “legacy” can be applied to both deleted
> bitstreams and items affected by the switch to uuids in DSpace 6?
> George
>
> On Tue, Apr 21, 2020 at 2:15 AM Bram Luyten  wrote:
>
>> Hi George,
>>
>> Emilio Lorenzo from Arvo.es sent me an off-list reply that I may have got
>> it wrong here.
>>
>> It's likely that legacy refers to the legacy item-id system, with
>> sequential ids (DSpace 5 and earlier), as opposed to the new uuid approach
>> since DSpace 6.
>>
>> This is discussed and documented here:
>> https://jira.lyrasis.org/browse/DS-3602
>>
>> I didn't look closely enough and was wrong in my initial reply. Thanks
>> again Emilio for the correction !!!
>>
>> cheers,
>>
>> Bram
>>
>> [image: logo] Bram Luyten
>> 250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586
>> 
>> Gaston Geenslaan 14, 3001 Leuven, Belgium
>> 
>> DSpace Express Hosting
>> 
>>  - Open Repository Hosting
>> 
>>  - Custom DSpace Services
>> 
>>
>>
>> On Mon, 20 Apr 2020 at 20:20, George Kozak  wrote:
>>
>>> Thanks you, Bram!  This was very helpful.
>>> George Kozak
>>> Cornell University
>>>
>>> On Mon, Apr 20, 2020 at 2:44 AM Bram Luyten  wrote:
>>>
 Hi George,

 the (legacy) note is added here:

 https://github.com/DSpace/DSpace/blob/820722d2e6e848a5b486c56b6596ce1473d16792/dspace-api/src/main/java/org/dspace/statistics/content/StatisticsDataVisits.java#L543

 By skimming through the code, I think it means that these are usage
 events that are still present in SOLR, while the original bitstream has
 been deleted.

 This seems to check out when looking at:
 https://ecommons.cornell.edu/handle/1813/7642

 The two public bitstreams have sequence IDs 4 and 6, meaning that you
 likely had additional bitstreams there, sequence id 1, 2, 3 and 5, and that
 those might be deleted?

 hope this helps,

 Bram

 [image: logo] Bram Luyten
 250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586
 
 Gaston Geenslaan 14, 3001 Leuven, Belgium
 
 DSpace Express Hosting
 
  - Open Repository Hosting
 
  - Custom DSpace Services
 


 On Mon, 20 Apr 2020 at 00:22, George Kozak  wrote:

> Hi,
> We are using DSpace 6.3 (XMLUI).  An author pointed out to us that the
> "View Usage Statistics" (
> https://ecommons.cornell.edu/handle/1813/7642/statistics) for his
> book in our DSpace has 2 categories:
> A ... 3549
> A ...(legacy) 755
>
> He asked what "legacy" means.  I wasn't sure, does someone know?
> Thanks!
> --
> ***
> George Kozak
> Digital Library Specialist
> Cornell University Library - IT
> 218 Olin Library
> Cornell University
> Ithaca, NY 14853
> 607-255-8924
> g...@cornell.edu
>
> *Due to staffing changes necessitated by the current public health
> concerns my response might be slower than usual. If your message is 
> urgent,
> please send it with the Subject header “URGENT”. Thank you!*
>
>>

[dspace-tech] making private during itemimport

[Jose Blanco]

Is there a way to make an item private when using the itemimport script in
6.3.  I could not find documentation on that.

Thank you!
-Jose

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CAK%3DKc-t-RyvHnXspJTkUkjMVgvMp1pw9pP44C5v5X65A%3DATgtA%40mail.gmail.com.

Re: [dspace-tech] The term "legacy" in Statistics

[Anne Lawrence]

We migrated from DSpace 5 to DSpace 6, and have the same display. We 
started the task of migrating the DSpace 5 and earlier stats to DSpace 6 
ones, as outlined in DS-3602, so they would all be in one category, but 
have not finished. I would add them together to determine the total 
downloads.

On Tuesday, April 21, 2020 at 8:23:20 AM UTC-4, George Kozak wrote:
>
> Thanks, again, Bram.
> So, am I right in assuming that “legacy” can be applied to both deleted 
> bitstreams and items affected by the switch to uuids in DSpace 6?
> George
>
> On Tue, Apr 21, 2020 at 2:15 AM Bram Luyten  > wrote:
>
>> Hi George,
>>
>> Emilio Lorenzo from Arvo.es sent me an off-list reply that I may have got 
>> it wrong here.
>>
>> It's likely that legacy refers to the legacy item-id system, with 
>> sequential ids (DSpace 5 and earlier), as opposed to the new uuid approach 
>> since DSpace 6.
>>
>> This is discussed and documented here: 
>> https://jira.lyrasis.org/browse/DS-3602
>>
>> I didn't look closely enough and was wrong in my initial reply. Thanks 
>> again Emilio for the correction !!!
>>
>> cheers,
>>
>> Bram
>>
>> [image: logo] Bram Luyten
>> 250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586 
>> 
>> Gaston Geenslaan 14, 3001 Leuven, Belgium 
>> 
>> DSpace Express Hosting 
>> 
>>  - Open Repository Hosting 
>> 
>>  - Custom DSpace Services 
>> 
>>
>>
>> On Mon, 20 Apr 2020 at 20:20, George Kozak > > wrote:
>>
>>> Thanks you, Bram!  This was very helpful.
>>> George Kozak
>>> Cornell University
>>>
>>> On Mon, Apr 20, 2020 at 2:44 AM Bram Luyten >> > wrote:
>>>
 Hi George,

 the (legacy) note is added here:

 https://github.com/DSpace/DSpace/blob/820722d2e6e848a5b486c56b6596ce1473d16792/dspace-api/src/main/java/org/dspace/statistics/content/StatisticsDataVisits.java#L543

 By skimming through the code, I think it means that these are usage 
 events that are still present in SOLR, while the original bitstream has 
 been deleted.

 This seems to check out when looking at:
 https://ecommons.cornell.edu/handle/1813/7642

 The two public bitstreams have sequence IDs 4 and 6, meaning that you 
 likely had additional bitstreams there, sequence id 1, 2, 3 and 5, and 
 that 
 those might be deleted?

 hope this helps,

 Bram

 [image: logo] Bram Luyten
 250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586 
 
 Gaston Geenslaan 14, 3001 Leuven, Belgium 
 
 DSpace Express Hosting 
 
  - Open Repository Hosting 
 
  - Custom DSpace Services 
 


 On Mon, 20 Apr 2020 at 00:22, George Kozak >>> > wrote:

> Hi,
> We are using DSpace 6.3 (XMLUI).  An author pointed out to us that the 
> "View Usage Statistics" (
> https://ecommons.cornell.edu/handle/1813/7642/statistics) for his 
> book in our DSpace has 2 categories:
> A ... 3549
> A ...(legacy) 755
>
> He asked what "legacy" means.  I wasn't sure, does someone know?
> Thanks! 
> -- 
> ***
> George Kozak
> Digital Library Specialist
> Cornell University Library - IT
> 218 Olin Library
> Cornell University
> Ithaca, NY 14853
> 607-255-8924
> gs...@cornell.edu  
>
> *Due to staffing changes necessitated by the current public health 
> concerns my response might be slower than usual. If your message is 
> urgent, 
> please send it with the Subject header “URGENT”. Thank you!*
>
 -- 
> All messages to this mailing list should adhere to the DuraSpace Code 
> of Conduct: https://duraspace.org/about/policies/code-of-conduct/
> --- 
> You received this message because you are subscribed to the Google 
> Groups "DSpace Technical Support" group.
> To unsubscribe from this group and stop receiving emails from it, send 
> an email to dspac...@googlegroups.com .
> To view this discussion

Re: [dspace-tech] The term "legacy" in Statistics

[George Kozak]

Thanks, again, Bram.
So, am I right in assuming that “legacy” can be applied to both deleted
bitstreams and items affected by the switch to uuids in DSpace 6?
George

On Tue, Apr 21, 2020 at 2:15 AM Bram Luyten  wrote:

> Hi George,
>
> Emilio Lorenzo from Arvo.es sent me an off-list reply that I may have got
> it wrong here.
>
> It's likely that legacy refers to the legacy item-id system, with
> sequential ids (DSpace 5 and earlier), as opposed to the new uuid approach
> since DSpace 6.
>
> This is discussed and documented here:
> https://jira.lyrasis.org/browse/DS-3602
>
> I didn't look closely enough and was wrong in my initial reply. Thanks
> again Emilio for the correction !!!
>
> cheers,
>
> Bram
>
> [image: logo] Bram Luyten
> 250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586
> 
> Gaston Geenslaan 14, 3001 Leuven, Belgium
> 
> DSpace Express Hosting
> 
>  - Open Repository Hosting
> 
>  - Custom DSpace Services
> 
>
>
> On Mon, 20 Apr 2020 at 20:20, George Kozak  wrote:
>
>> Thanks you, Bram!  This was very helpful.
>> George Kozak
>> Cornell University
>>
>> On Mon, Apr 20, 2020 at 2:44 AM Bram Luyten  wrote:
>>
>>> Hi George,
>>>
>>> the (legacy) note is added here:
>>>
>>> https://github.com/DSpace/DSpace/blob/820722d2e6e848a5b486c56b6596ce1473d16792/dspace-api/src/main/java/org/dspace/statistics/content/StatisticsDataVisits.java#L543
>>>
>>> By skimming through the code, I think it means that these are usage
>>> events that are still present in SOLR, while the original bitstream has
>>> been deleted.
>>>
>>> This seems to check out when looking at:
>>> https://ecommons.cornell.edu/handle/1813/7642
>>>
>>> The two public bitstreams have sequence IDs 4 and 6, meaning that you
>>> likely had additional bitstreams there, sequence id 1, 2, 3 and 5, and that
>>> those might be deleted?
>>>
>>> hope this helps,
>>>
>>> Bram
>>>
>>> [image: logo] Bram Luyten
>>> 250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586
>>> 
>>> Gaston Geenslaan 14, 3001 Leuven, Belgium
>>> 
>>> DSpace Express Hosting
>>> 
>>>  - Open Repository Hosting
>>> 
>>>  - Custom DSpace Services
>>> 
>>>
>>>
>>> On Mon, 20 Apr 2020 at 00:22, George Kozak  wrote:
>>>
 Hi,
 We are using DSpace 6.3 (XMLUI).  An author pointed out to us that the
 "View Usage Statistics" (
 https://ecommons.cornell.edu/handle/1813/7642/statistics) for his book
 in our DSpace has 2 categories:
 A ... 3549
 A ...(legacy) 755

 He asked what "legacy" means.  I wasn't sure, does someone know?
 Thanks!
 --
 ***
 George Kozak
 Digital Library Specialist
 Cornell University Library - IT
 218 Olin Library
 Cornell University
 Ithaca, NY 14853
 607-255-8924
 g...@cornell.edu

 *Due to staffing changes necessitated by the current public health
 concerns my response might be slower than usual. If your message is urgent,
 please send it with the Subject header “URGENT”. Thank you!*

>>> --
 All messages to this mailing list should adhere to the DuraSpace Code
 of Conduct: https://duraspace.org/about/policies/code-of-conduct/
 ---
 You received this message because you are subscribed to the Google
 Groups "DSpace Technical Support" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to dspace-tech+unsubscr...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/dspace-tech/CAB8VfOCpfA7SfxokRSnS2-E28MUM03%2BQvEm5VV7ddemVGydkTQ%40mail.gmail.com
 
 .

>>>
>>
>> --
>> ***
>> George Kozak
>> Digital Library Specialist
>> Cornell University Library - IT
>> 218 Olin Library
>> Cornell University
>> Ithaca, NY 14853
>> 607-255-8924
>> g...@cornell.edu
>>