[dspace-tech] Re: item access conditions step configuration

2022-11-02 Thread 'Tim Donohue' via DSpace Technical Support
Hi Bill,

The "access conditions" that appear in the Submission Form after you click 
Edit on a file are configured in the new "access-conditions.xml" Spring 
configuration file.  See the docs 
here: 
https://wiki.lyrasis.org/display/DSDOC7x/Submission+User+Interface#SubmissionUserInterface-Modifyingaccessconditions(embargo,etc.)presentedforBitstreams

I suspect that's what you are looking for. 

While I haven't tried it myself, I think you can disable to access 
conditions by commenting out the "options" in that configuration...or maybe 
just provide the "openAccess" option if that's the one you want.

Tim

On Wednesday, November 2, 2022 at 7:29:58 AM UTC-5 tant...@umn.edu wrote:

> Sorry, just wanted to bump this up to see if anybody has any experience 
> with this configuration?
> Thanks for looking,
> ~~Bill
>
> On Friday, October 28, 2022 at 9:01:38 AM UTC-5 tant...@umn.edu wrote:
>
>> In DSpace 7.4, I would like to NOT display the Access Conditions step on 
>> my "Edit bitstream" form.  It is not enabled in my  
>> definition, nor anywhere else in item-submission.xml (according to the 
>> documentation, it is disabled by default).  However, I still see dropdowns 
>> for
>>
>> Access condition type
>> Grant access from
>> Grant access until
>>
>> on my form.  Is there a way to suppress this?
>> Thanks,
>> ~~Bill
>> -- 
>> Human wheels spin round and round
>> While the clock keeps the pace... -- John Mellencamp
>> 
>> Bill TantzenUniversity of Minnesota Libraries
>> 612-626-9949 <(612)%20626-9949> (U of M)612-325-1777 
>> <(612)%20325-1777> (cell)
>>
>

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
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/2f7196a6-3619-43c4-9453-9656596df7e7n%40googlegroups.com.


[dspace-tech] Re: Importing sharded solr statistics in DSpace 7

2022-11-02 Thread 'Tim Donohue' via DSpace Technical Support

Hi Karol,

Yes, you *should* be able to combine older sharded/split statistics by 
exporting those stats (using "solr-export-statistics") to CSV, an then 
importing them into your new Solr (using "solr-import-statistics").  By 
default that "solr-import-statistics" script would just add the new 
statistics to your Solr (just make sure not to specify the "clear" flag 
which would completely delete all current stats before importing the new 
ones).  See the docs 
at https://wiki.lyrasis.org/display/DSDOC7x/SOLR+Statistics+Maintenance

As always, I'd recommend testing this process before doing it in 
Production. But it seems to me like it should work.

After responding to your earlier question about shards, I realized we have 
a known bug with loading statistics from shards in DSpace 7.  
See https://github.com/DSpace/DSpace/issues/8478   That is scheduled to be 
analyzed/fixed, but I don't yet know when (as it's still waiting on a 
volunteer).   We also have a note to the official docs about ongoing 
sharding, as it's likely that any sharding decisions need to be made based 
on your local Solr setup/needs (and any sharding likely should be done 
using Solr tools themselves).  See note 
at 
https://wiki.lyrasis.org/display/DSDOC7x/SOLR+Statistics+Maintenance#SOLRStatisticsMaintenance-SolrShardingByYear

If you have other questions, let us know on this list.

Tim
On Tuesday, November 1, 2022 at 3:45:16 PM UTC-5 karols...@gmail.com wrote:

> Hi Tim,
>
> As usual, thank you for your reply. Indeed, there was no statistics-2021 
> folder in my "solr/configsets/". Can you tell me if I created 
> statistics-2021 in the correct way?
>
> 1) I copied /solr/configsets/statistics to /solr/configsets/statistics-2021
> 2) I made the import with the script: solr-import-statistics -i 
> statistics-2021 
> Now the import error does not appear.
>
> Is this not a good practice and need to do it differently? E.g. through 
> the solr web panel?
>
> Alternatively, is it possible to merge the split statistics by changing 
> all exported files from the split year, e.g: 
> statistics-2021_export_2021-05_31.csv to statistics_export_2021-05_31.csv 
> and import with the master script: 
> /dspace/bin/dspace solr-import-statistics -i statistics 
> ?
>
> Thanks and best regards,
>
> Karol
>
>
> wtorek, 1 listopada 2022 o 15:08:57 UTC+1 Tim Donohue napisaƂ(a):
>
>> Hi,
>>
>> That appears to be saying that the Solr service at 
>> http://localhost:8983/solr/statistics-2021 is not responding or doesn't 
>> exist?  It looks like you are getting a 404 from that URL.  So, you should 
>> verify that URL is correct and that it is accessible to you.
>>
>> Tim
>>
>> On Sunday, October 30, 2022 at 6:52:19 AM UTC-5 karols...@gmail.com 
>> wrote:
>>
>>> Hi,
>>>
>>> I am trying to migrate solr stats from dspace 6.3 to 7.4. Importing 2022 
>>> - current stats works without any problem, the problem occurs when I try to 
>>> import 2019,2020,2021(sharded stats):
>>> /dspace/bin/dspace solr-import-statistics -i statistics-2021
>>>   
>>> Exception: Error from server at 
>>> http://localhost:8983/solr/statistics-2021: Expected mime type 
>>> application/octet-stream but got text/html. 
>>> 
>>> 
>>> Error 404 Not Found
>>> 
>>> HTTP ERROR 404 Not Found
>>> 
>>> URI:/solr/statistics-2021/admin/luke
>>> STATUS:404
>>> MESSAGE:Not Found
>>> SERVLET:default
>>> 
>>>
>>> 
>>> 
>>>
>>> org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: 
>>> Error from server at http://localhost:8983/solr/statistics-2021: 
>>> Expected mime type application/octet-stream but got text/html. 
>>> 
>>> 
>>> Error 404 Not Found
>>> 
>>> HTTP ERROR 404 Not Found
>>> 
>>> URI:/solr/statistics-2021/admin/luke
>>> STATUS:404
>>> MESSAGE:Not Found
>>> SERVLET:default
>>> 
>>>
>>> 
>>> 
>>>
>>> at 
>>> org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:635)
>>> at 
>>> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:266)
>>> at 
>>> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:248)
>>> at 
>>> org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:214)
>>> at 
>>> org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:231)
>>> at 
>>> org.dspace.util.SolrImportExport.getMultiValuedFields(SolrImportExport.java:482)
>>> at 
>>> org.dspace.util.SolrImportExport.importIndex(SolrImportExport.java:433)
>>> at 
>>> org.dspace.util.SolrImportExport.main(SolrImportExport.java:148)
>>> 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)
>>> 

[dspace-tech] Re: item access conditions step configuration

2022-11-02 Thread 'tant...@umn.edu' via DSpace Technical Support
Sorry, just wanted to bump this up to see if anybody has any experience 
with this configuration?
Thanks for looking,
~~Bill

On Friday, October 28, 2022 at 9:01:38 AM UTC-5 tant...@umn.edu wrote:

> In DSpace 7.4, I would like to NOT display the Access Conditions step on 
> my "Edit bitstream" form.  It is not enabled in my  
> definition, nor anywhere else in item-submission.xml (according to the 
> documentation, it is disabled by default).  However, I still see dropdowns 
> for
>
> Access condition type
> Grant access from
> Grant access until
>
> on my form.  Is there a way to suppress this?
> Thanks,
> ~~Bill
> -- 
> Human wheels spin round and round
> While the clock keeps the pace... -- John Mellencamp
> 
> Bill TantzenUniversity of Minnesota Libraries
> 612-626-9949 <(612)%20626-9949> (U of M)612-325-1777 
> <(612)%20325-1777> (cell)
>

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
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/7daa216a-8428-491e-9652-2ce96fe9757bn%40googlegroups.com.


Re: [dspace-tech] Re: Is it advised to comment out ehcache updateCheck

2022-11-02 Thread Mark H. Wood
On Tue, Nov 01, 2022 at 07:16:33AM -0700, 'Tim Donohue' via DSpace Technical 
Support wrote:
> Hi Sarah,
> 
> The context of your question is unclear.  But, I wanted to note that this 
> configuration has been fully removed from DSpace 7 (as of 7.3, 
> see https://github.com/DSpace/DSpace/pull/8146).  So, that 
> "dspace-services/src/main/resources/caching/ehcache-config.xml" file no 
> longer exists in DSpace 7.
> 
> It's unclear what version of DSpace you are referring to.  I was personally 
> unaware that this configuration caused any issues in older versions of 
> DSpace, but it appears that at least Alan Orth (and maybe others) found 
> that setting "updateCheck=false" helped.  So, I cannot make a 
> recommendation here as to whether to change that setting or not in older 
> DSpace releases... but maybe others can provide more specific advise.

DSpace was patched on 2018-04-08 to disable the update check.
See https://github.com/DSpace/DSpace/pull/1940

I recall that the messages were annoying and the check slowed startup
a bit.

> On Monday, October 31, 2022 at 6:40:20 AM UTC-5 sbu...@oakland.edu wrote:
> 
> > Hello,
> >
> > In this update from Alan  
> > https://alanorth.github.io/cgspace-notes/2017-09/#2017-09-12, it is 
> > suggested that setting this updateCheck="false" resolves an issue of 
> > frequent calls to terracotta (we are seeing this issue).  Is it still 
> > advisable to make this change?
> >
> > Thanks!
> > Sarah

-- 
Mark H. Wood
Lead Technology Analyst

University Library
Indiana University - Purdue University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-0749
www.ulib.iupui.edu

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
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/Y2JORAajwSb%2B2J1B%40IUPUI.Edu.


signature.asc
Description: PGP signature