[dspace-tech] Request for assistance with configuring DSpace 7.4 for OAuth authorization

[tarun kumar]

I am writing to request your assistance with configuring DSpace 7.4 for 
OAuth authorization. Providing guidance on how to incorporate OAuth 
authorization in our DSpace instance.

Regards
Tarun

-- 
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/6b96072f-e74d-4183-bd73-530133d1a0d9n%40googlegroups.com.

Re: [dspace-tech] Set up Dspace 7.2

[Oumar Fara Biram LO]

Hello, thank you for your promptness. Can you please provide me with the
summary manual for the installation of Dspace 7.5 on Ubuntu 20.0.4 with
support for all prerequisites? I am having trouble with the manual
available on the website.

Le jeu. 13 avr. 2023 à 11:52, Mark H. Wood  a écrit :

> On Wed, Apr 12, 2023 at 08:19:16AM -0700, LSBU wrote:
> > Hello, I would like to know some parameters for my Dspace 7.2:
>
> That is quite outdated now.  You should consider upgrading to 7.5 at
> your earliest convenience.
>
> > 1- How to create a user group on the terminal ?
>
> That is not implemented.
>
> > 2- how to add a user on the terminal ?
>
> 'bin/dspace user --add --help' will show you the options.  'bin/dspace
> user --help' will show you other things you can do with user accounts
> from the command line.
>
> The 'user' command is documented at
> https://wiki.lyrasis.org/display/DSDOC7x/Managing+User+Accounts
>
> The command line tools are summarized at
> https://wiki.lyrasis.org/display/DSDOC7x/Command+Line+Operations
>
> > 3- how to import users from the terminal ?
>
> You can make a script of 'add' commands and run it with 'bin/dspace read'.
>
> > 4- what are the services to start after restarting the server to make
> > Dspace functional ?
>
> You will need your Servlet container (usually Tomcat), Solr, and the
> DBMS (usually PostgreSQL).  If you have registered with the Handle
> Service then you will also want to run the local Handle resolver.
>
> > 5- how to automate these services so that they start automatically at
> > server startup ?
>
> That depends on your operating system.  What are you running?
>
> > 6- how to improve response times if we perform a search from the
> portal.5 ?
>
> I don't understand "portal.5".
>
> > 7- What are the data and configuration files to backup so that in case
> of a
> > problem, we can restore our database?
>
> You need to back up the assetstore directories and a dump of the
> database.
>
> The DBMS has tools to dump and restore databases, and this is how you
> should back them up.  It is nearly impossible to get a consistent
> backup of most database products' content by saving their raw files.
>
> The assetstore can be backed up as-is.
>
> You will also want to back up 'config/' and its subdirectories.
>
> You should also consider
> https://wiki.lyrasis.org/display/DSDOC7x/AIP+Backup+and+Restore
>
> --
> 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 a topic in the
> Google Groups "DSpace Technical Support" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/dspace-tech/uC0wIRXRTs8/unsubscribe.
> To unsubscribe from this group and all its topics, 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/ZDfs9i1Q6l1o%2BIMh%40IUPUI.Edu
> .
>
-- 
Oumar LO
Bureau Technique Logistique
Bibliothèque Centrale
Université Gaston Berger

-- 
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/CANYhEuSkiH%2BuPFtJ%2BJ%2Bc%3DodU%2BqMgtRcMgu%2BxigUkaHhDOxfVFA%40mail.gmail.com.

[dspace-tech] Re: Permanent URI for this community http://localhost:4000/handle/...

[darryl....@usask.ca]

Have a look at the handle.canonical.prefix and handle.prefix in your 
local.cfg file.  There's some documentation (in the form of comments) in 
dspace.cfg and also 
here: https://wiki.lyrasis.org/display/DSDOC7x/Configuration+Reference in 
the Handle Server Configuration section.

The default value for handle.canonical.prefix  is  ${dspace.ui.url}/handle/ and 
your dspace.ui.url must be http://localhost:4000 which is why you are 
seeing community/collections URLs like that.

- Darryl


On Thursday, April 13, 2023 at 12:11:38 PM UTC-6 Costantino, Fernán wrote:

> Hi, I was trying to understand how to fix this.
>
> "Permanent URI for this community" link to http://localhost:4000/handle/... 
> instead of dspace.ui.url (dspace.cfg)
>
> There are some discussions/issues on github (for example: 
> https://github.com/DSpace/dspace-angular/issues/887 ), but is difficult 
> to me to follow the thread. Can someone explain the procedure to solve it? 
> It seems that I need to modify some code? Thanks.
> -- 
>
> *Costantino, Fernán*
> División Nuevas Tecnologías
> Biblioteca Central Francisco P. Moreno
> Universidad Nacional del Comahue
> Santa Fe y Leloir (Q8300) Neuquén Cap.- Tel 54(0299)4490398
>
>

-- 
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/52edda77-b00c-4c12-b09e-8de5937acf26n%40googlegroups.com.

[dspace-tech] [DSpace Angular] Adding new modules & routes to RouterModule from a theme

[Abel Gómez]

Hi all,

I've been working on a theme and customization for DSpace 7, and I've 
stumbled upon a problem I'm not really sure whether it's solvable or not.

I'd like to add some additional routes and modules to serve some additional 
sections in the DSpace site (mostly static HTML) but keeping the look and 
feel of my custom theme, and keeping the breadcrumbs and navigation 
features if possible. After inspecting the code, I've figured out the way 
to do it by modifying the "base app" (e.g., AppRoutingModule, and adding 
the needed modules under src/app/...), but I'd like to keep my 
modifications as modular and isolated as possible.

Is there any way to achieve the same by modifying only my custom theme in 
"src/themes/mytheme", and without changing the "base code" of DSpace 
angular in "src/app"?

Thanks for your help and advise.

Cheers,

Abel



-- 
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/5c374cd0-3d77-4763-b6b6-3adfe74d2749n%40googlegroups.com.

Re: [dspace-tech] Re: Angular "dspace-ui-deploy" directory large "core.*" files

[hb wooley]

Hardy,
That is great information. Thanks

hbwooley
On Thursday, April 13, 2023 at 2:52:06 PM UTC-5 Hardy Pottinger wrote:

> Hi, while core dumps can be helpful for troubleshooting, if you're 
> simply deleting these files without looking at them, you might 
> consider disabling core dump creation. Here's a writeup on how:
>
>
> https://www.cyberciti.biz/faq/disable-core-dumps-in-linux-with-systemd-sysctl/
>
> I am not recommending that you do this, it's up to you. But... it's an 
> option.
>
> --Hardy
>
> On Thu, Apr 13, 2023 at 2:45 PM hb wooley  wrote:
>
>> The server might be doing as you said, I really haven't tuned it and the 
>> server is a development server without many resources.  I did checkout the 
>> link and it sounds like this could be the issue, thank you for the insight.
>>
>> hbwooley
>> On Thursday, April 13, 2023 at 1:47:03 PM UTC-5 Tim Donohue wrote:
>>
>>> Hi,
>>>
>>> Those "core.*" files are not being created by DSpace.   DSpace never 
>>> writes/creates new files to that folder once it is running.
>>>
>>> It's likely those are memory dumps created by Linux.  It sounds like 
>>> some process (maybe Node.js, or whatever else you are using the run the 
>>> DSpace UI?) is running out of memory and/or crashing frequently. That is 
>>> likely what is creating these "core.*" files.  See this StackOverflow for 
>>> example: https://stackoverflow.com/a/20530587/3750035
>>>
>>> Tim
>>>
>>> On Thursday, April 13, 2023 at 1:01:26 PM UTC-5 bwe...@gmail.com wrote:
>>>
 Forgot I'm using dspace-angular 7.5

 On Thursday, April 13, 2023 at 12:59:38 PM UTC-5 hb wooley wrote:

> Hoping someone can help.
> Under the Angular "dspace-ui-deploy" directory where you copy the 
> Angular "dist" folder, I'm seeing large core.* files. These (binary) 
> files 
> keep growing in this directory, can someone tell me what these files are 
> for and can the number of them be limited, since they can fill up a drive 
> if not monitored?
> Example:
> 2.3G Mar 24 15:28 core.18471
> 2.3G Mar 25 00:58 core.23446
> 2.3G Mar 25 21:18 core.10618
> 2.3G Mar 26 22:59 core.3294
> 2.3G Mar 28 01:15 core.19507
> 2.3G Mar 28 12:49 core.16889
> 2.4G Mar 30 12:30 core.3287
> 2.3G Apr  1 00:25 core.4652
> 2.3G Apr  3 14:10 core.7601
> 2.3G Apr  5 00:59 core.28903
> 2.3G Apr  5 19:18 core.12439
> 2.3G Apr  7 09:17 core.9281
> 2.3G Apr  8 00:19 core.6379
> 2.3G Apr  8 00:49 core.7008
> 2.3G Apr  8 12:25 core.18488
> 2.3G Apr  9 12:23 core.32223
> 2.3G Apr 10 12:23 core.1507
> 2.3G Apr 11 20:29 core.3029
> 2.3G Apr 13 12:22 core.6437
>
> Thank you -
>
 -- 
>> 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...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/dspace-tech/d5923f59-2012-4c6a-a736-4c5c067adeb4n%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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/86d9cfcd-4ae5-48c3-8be2-b13579b52003n%40googlegroups.com.

Re: [dspace-tech] Re: Angular "dspace-ui-deploy" directory large "core.*" files

[Hardy Pottinger]

Hi, while core dumps can be helpful for troubleshooting, if you're
simply deleting these files without looking at them, you might
consider disabling core dump creation. Here's a writeup on how:

https://www.cyberciti.biz/faq/disable-core-dumps-in-linux-with-systemd-sysctl/

I am not recommending that you do this, it's up to you. But... it's an
option.

--Hardy

On Thu, Apr 13, 2023 at 2:45 PM hb wooley  wrote:

> The server might be doing as you said, I really haven't tuned it and the
> server is a development server without many resources.  I did checkout the
> link and it sounds like this could be the issue, thank you for the insight.
>
> hbwooley
> On Thursday, April 13, 2023 at 1:47:03 PM UTC-5 Tim Donohue wrote:
>
>> Hi,
>>
>> Those "core.*" files are not being created by DSpace.   DSpace never
>> writes/creates new files to that folder once it is running.
>>
>> It's likely those are memory dumps created by Linux.  It sounds like some
>> process (maybe Node.js, or whatever else you are using the run the DSpace
>> UI?) is running out of memory and/or crashing frequently. That is likely
>> what is creating these "core.*" files.  See this StackOverflow for example:
>> https://stackoverflow.com/a/20530587/3750035
>>
>> Tim
>>
>> On Thursday, April 13, 2023 at 1:01:26 PM UTC-5 bwe...@gmail.com wrote:
>>
>>> Forgot I'm using dspace-angular 7.5
>>>
>>> On Thursday, April 13, 2023 at 12:59:38 PM UTC-5 hb wooley wrote:
>>>
 Hoping someone can help.
 Under the Angular "dspace-ui-deploy" directory where you copy the
 Angular "dist" folder, I'm seeing large core.* files. These (binary) files
 keep growing in this directory, can someone tell me what these files are
 for and can the number of them be limited, since they can fill up a drive
 if not monitored?
 Example:
 2.3G Mar 24 15:28 core.18471
 2.3G Mar 25 00:58 core.23446
 2.3G Mar 25 21:18 core.10618
 2.3G Mar 26 22:59 core.3294
 2.3G Mar 28 01:15 core.19507
 2.3G Mar 28 12:49 core.16889
 2.4G Mar 30 12:30 core.3287
 2.3G Apr  1 00:25 core.4652
 2.3G Apr  3 14:10 core.7601
 2.3G Apr  5 00:59 core.28903
 2.3G Apr  5 19:18 core.12439
 2.3G Apr  7 09:17 core.9281
 2.3G Apr  8 00:19 core.6379
 2.3G Apr  8 00:49 core.7008
 2.3G Apr  8 12:25 core.18488
 2.3G Apr  9 12:23 core.32223
 2.3G Apr 10 12:23 core.1507
 2.3G Apr 11 20:29 core.3029
 2.3G Apr 13 12:22 core.6437

 Thank you -

>>> --
> 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/d5923f59-2012-4c6a-a736-4c5c067adeb4n%40googlegroups.com
> 
> .
>

-- 
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/CAAf%2BQRZomNeZkhsL_bz%3D6E9%3D5TFU0nPoNNLYvyf5ThPTKxK8gA%40mail.gmail.com.

[dspace-tech] Re: Angular "dspace-ui-deploy" directory large "core.*" files

[hb wooley]

The server might be doing as you said, I really haven't tuned it and the 
server is a development server without many resources.  I did checkout the 
link and it sounds like this could be the issue, thank you for the insight.

hbwooley
On Thursday, April 13, 2023 at 1:47:03 PM UTC-5 Tim Donohue wrote:

> Hi,
>
> Those "core.*" files are not being created by DSpace.   DSpace never 
> writes/creates new files to that folder once it is running.
>
> It's likely those are memory dumps created by Linux.  It sounds like some 
> process (maybe Node.js, or whatever else you are using the run the DSpace 
> UI?) is running out of memory and/or crashing frequently. That is likely 
> what is creating these "core.*" files.  See this StackOverflow for example: 
> https://stackoverflow.com/a/20530587/3750035
>
> Tim
>
> On Thursday, April 13, 2023 at 1:01:26 PM UTC-5 bwe...@gmail.com wrote:
>
>> Forgot I'm using dspace-angular 7.5
>>
>> On Thursday, April 13, 2023 at 12:59:38 PM UTC-5 hb wooley wrote:
>>
>>> Hoping someone can help.
>>> Under the Angular "dspace-ui-deploy" directory where you copy the 
>>> Angular "dist" folder, I'm seeing large core.* files. These (binary) files 
>>> keep growing in this directory, can someone tell me what these files are 
>>> for and can the number of them be limited, since they can fill up a drive 
>>> if not monitored?
>>> Example:
>>> 2.3G Mar 24 15:28 core.18471
>>> 2.3G Mar 25 00:58 core.23446
>>> 2.3G Mar 25 21:18 core.10618
>>> 2.3G Mar 26 22:59 core.3294
>>> 2.3G Mar 28 01:15 core.19507
>>> 2.3G Mar 28 12:49 core.16889
>>> 2.4G Mar 30 12:30 core.3287
>>> 2.3G Apr  1 00:25 core.4652
>>> 2.3G Apr  3 14:10 core.7601
>>> 2.3G Apr  5 00:59 core.28903
>>> 2.3G Apr  5 19:18 core.12439
>>> 2.3G Apr  7 09:17 core.9281
>>> 2.3G Apr  8 00:19 core.6379
>>> 2.3G Apr  8 00:49 core.7008
>>> 2.3G Apr  8 12:25 core.18488
>>> 2.3G Apr  9 12:23 core.32223
>>> 2.3G Apr 10 12:23 core.1507
>>> 2.3G Apr 11 20:29 core.3029
>>> 2.3G Apr 13 12:22 core.6437
>>>
>>> Thank you -
>>>
>>

-- 
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/d5923f59-2012-4c6a-a736-4c5c067adeb4n%40googlegroups.com.

Re: [dspace-tech] DSpace 7.5 Solr Statistics migration from 5.10 with sharding by year

['Tim Donohue' via DSpace Technical Support]

Thanks James & Tomas for sharing your hints/tips here!  It's obvious we 
didn't document this very well in the DSpace 7 Upgrade process.  Just now, 
I've done my best to summarize your advice & add more hints in Step 10(a) 
of the Upgrade process to help others along. I even linked folks back to 
this useful dspace-tech thread for more details.

https://wiki.lyrasis.org/display/DSDOC7x/Upgrading+DSpace

If others have hints/tips to share, please do feel free to continue this 
thread, or add comments to the docs & we'll get them taken into account.

Tim

On Thursday, April 13, 2023 at 1:54:47 PM UTC-5 ha...@oakland.edu wrote:

> Thanks for the information.  I had similar information sent to me by 
> another person on the list so it seems we are all approaching this about 
> the same way.  I think I have my statistics imported at this point.  
> To rename the statistics files I wound up using the following one liner: 
> cd /opt/dspace/solr-export; for i in $(ls *.csv); do nf=$(echo $i | sed 
> 's/-20[1-2][0-9]_e/_e/g'); mv -v $i $nf; done
>
> Another suggestion was to use rename (e.g. rename 
> "s/-2015_export/_export/g"  *) but for whatever reason that was not 
> working for me on my RHEL 8.7 server.
> After renaming the files and running /opt/dspace/bin/dspace 
> solr-import-statistics -i statistics it looks like I have the statistics 
> imported.
>
> Thanks for the help.
> -Tomas
>
> On Tue, Apr 4, 2023 at 11:25 AM James Holobetz  wrote:
>
>> Hi Tomas,
>>
>> I recently had this issue and I believe that I have found a solution, 
>> which I will document in the next few days. The long and the short of it is 
>> that DSpace 7 does not support solr shards. You have to create one large 
>> solr shard (statistics) from the multiple shards. The biggest problem I 
>> found doing this was that DSpace was only ingesting the current year 
>> statistics only. The solution was to rename the *csv files that are 
>> dumped by solr-export-statistics. For example: the csv files for the solr 
>> core 
>> "statistics-2012" will look something like this -- 
>> statistics-2012_export_2013-12_5.csv. 
>> You have to rename all the csv files to remove the -2012 in the filename to 
>> look like this: statistics_export_2013-12_5.csv. I downloaded the zipped up 
>> cores in csv form to my windows machine so I could use a bulk rename tool 
>> to remove the year suffix in each core. I then uploaded them to my linux 
>> box running DSpace and ingested each one using the solr-import-statistics 
>> tool. 
>> This is a very time consuming task.
>>
>> Hope this helps and I will try to document this in the next few days.
>>
>> Best regards,
>>
>> James Holobetz
>>
>> On Fri, Mar 24, 2023 at 3:37 PM Tomas Hajek  wrote:
>>
>>> Hello, 
>>>I am working on migrating a DSpace 5.10 installation to a new server 
>>> running DSpace 7.5.  I have the basic installation running on RHEL 8.7 with 
>>> Tomcat 9.0.71, Solr 8.11.2, node.js 16.18.1, and pm2 5.2.2.  
>>> I was able to import the database and assetstore and I set up the Solr 
>>> cores (authority,oai,search,statistics) from the installation instructions.
>>>The Solr statistics from the 5.10 installation are sharded by year 
>>> and I exported with the following:
>>>
>>> bin/dspace solr-export-statistics -i statistics-2015
>>> bin/dspace solr-export-statistics -i statistics-2016
>>> ...
>>> bin/dspace solr-export-statistics -i statistics-2022
>>>
>>> I have copied the exported files to the new 7.5 server 
>>> into /opt/dspace/solr-export and am trying to import them but I get the 
>>> following error (example when trying to import the 2015 statistics):
>>>
>>> /opt/dspace/bin/dspace solr-import-statistics -i statistics-2015
>>> Exception: Error from server at 
>>> http://localhost:8983/solr/statistics-2015: Expected mime type 
>>> application/octet-stream but got text/html. 
>>> 
>>> 
>>> Error 404 Not Found
>>> 
>>> HTTP ERROR 404 Not Found
>>> 
>>> URI:/solr/statistics-2015/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-2015: 
>>> Expected mime type application/octet-stream but got text/html. 
>>> 
>>> 
>>> Error 404 Not Found
>>> 
>>> HTTP ERROR 404 Not Found
>>> 
>>> URI:/solr/statistics-2015/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 
>>> 

Re: [dspace-tech] Disk partitioning for DSpace 7

[Andrew K]

Hello Mark,

Thanks a lot for the comprehensive reply and valuable insights. I will try 
to implement. Might need to start over with the server, though. Or wait and 
see how it goes first.

Best regards,
Andrew

середа, 12 квітня 2023 р. о 15:38:42 UTC+3 Mark H. Wood пише:

On Tue, Apr 11, 2023 at 08:56:07AM -0700, Andrew K wrote: 
> What is the optimum disk partitioning for DSpace 7? 

"Optimum" will be strongly dependent on (a) your OS and (b) how much 
you are storing in your repository. 

> I use a VDS, so the space is important. The aim is to have the system 
> partition 20-30GB and keep everything else on another partition, 
including 
> logs (they are very important AFAIK).. 

That seems sensible. 

I don't think anyone is going to have a "best way" for you, but here's 
what I've done. 

o I like to keep the Solr cores and the database each on its own 
volume. That way /var can fill up with log files and not stop 
DSpace. (These days, the DBMS is on a separate host, and I'd like 
to move Solr to yet another since they tend to become busy at the 
same time.) 

o I invented a configuration parameter 'dspace.var' and use it 
throughout the configuration, wherever DSpace is configured to 
store volatile files such as exported materials and the assetstore. 
Code and configuration are installed on the /opt volume and the 
rest is mounted on /var/lib/dspace. This last is again a separate 
volume. 

I've installed Monit to keep Tomcat, Solr and PostgreSQL running, 
monitor availability, restart anything that gets wedged, and email me 
if there's anything it can't handle. I also have the critical storage 
volumes monitored in case one comes close to filling up. 

I strongly recommend using a logical volume layer on top of a very 
simple physical partitioning scheme, so that you can add physical 
volumes online and portion them out as needed when logical volumes 
fill up. Usually I'll set up physical partitions "/" and "/boot", and 
make all the rest a single LVM PV partition, leaving some uncommitted 
storage in case I need to expand an LV more quickly than our corporate 
virtual-machine infrastructure can respond to my request. If I need 
to add physical storage, I can join it to the existing volume group, 
add slices to LVs as needed, and expand the LVs' filesystems into the 
new extents, all without interrupting service. (You don't need to 
understand *all* of that on Day 1, but getting the basics done at 
installation will make life so much nicer as the repository grows.) 

I need to say that usually on a new host I'll take a wild guess about 
how much storage will be needed for each of these various functions, 
then adjust when I see how the system is really operating. Some of my 
guesses have been quite over-generous. It's much harder to shrink a 
volume than to expand one, even on LVM. These days I'd probably 
request just as much physical storage, but leave more of it 
uncommitted and watch growth more closely. 

In the end, only a running system can tell you *precisely* what it 
needs to function adequately and reliably. Provide yourself with good 
system management tools and the ability to readily add capacity if you 
need it. Always give your systems a thorough inspection for capacity 
as annual budget time approaches. 

-- 
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/7af8070a-15a8-44b7-ad15-19022fb8d7a8n%40googlegroups.com.

Re: [dspace-tech] DSpace 7.5 Solr Statistics migration from 5.10 with sharding by year

[Tomas Hajek]

Thanks for the information.  I had similar information sent to me by
another person on the list so it seems we are all approaching this about
the same way.  I think I have my statistics imported at this point.
To rename the statistics files I wound up using the following one liner:
cd /opt/dspace/solr-export; for i in $(ls *.csv); do nf=$(echo $i | sed
's/-20[1-2][0-9]_e/_e/g'); mv -v $i $nf; done

Another suggestion was to use rename (e.g. rename
"s/-2015_export/_export/g"  *) but for whatever reason that was not working
for me on my RHEL 8.7 server.
After renaming the files and running /opt/dspace/bin/dspace
solr-import-statistics -i statistics it looks like I have the statistics
imported.

Thanks for the help.
-Tomas

On Tue, Apr 4, 2023 at 11:25 AM James Holobetz  wrote:

> Hi Tomas,
>
> I recently had this issue and I believe that I have found a solution,
> which I will document in the next few days. The long and the short of it is
> that DSpace 7 does not support solr shards. You have to create one large
> solr shard (statistics) from the multiple shards. The biggest problem I
> found doing this was that DSpace was only ingesting the current year
> statistics only. The solution was to rename the *csv files that are
> dumped by solr-export-statistics. For example: the csv files for the solr core
> "statistics-2012" will look something like this -- 
> statistics-2012_export_2013-12_5.csv.
> You have to rename all the csv files to remove the -2012 in the filename to
> look like this: statistics_export_2013-12_5.csv. I downloaded the zipped up
> cores in csv form to my windows machine so I could use a bulk rename tool
> to remove the year suffix in each core. I then uploaded them to my linux
> box running DSpace and ingested each one using the solr-import-statistics 
> tool.
> This is a very time consuming task.
>
> Hope this helps and I will try to document this in the next few days.
>
> Best regards,
>
> James Holobetz
>
> On Fri, Mar 24, 2023 at 3:37 PM Tomas Hajek  wrote:
>
>> Hello,
>>I am working on migrating a DSpace 5.10 installation to a new server
>> running DSpace 7.5.  I have the basic installation running on RHEL 8.7 with
>> Tomcat 9.0.71, Solr 8.11.2, node.js 16.18.1, and pm2 5.2.2.
>> I was able to import the database and assetstore and I set up the Solr
>> cores (authority,oai,search,statistics) from the installation instructions.
>>The Solr statistics from the 5.10 installation are sharded by year and
>> I exported with the following:
>>
>> bin/dspace solr-export-statistics -i statistics-2015
>> bin/dspace solr-export-statistics -i statistics-2016
>> ...
>> bin/dspace solr-export-statistics -i statistics-2022
>>
>> I have copied the exported files to the new 7.5 server
>> into /opt/dspace/solr-export and am trying to import them but I get the
>> following error (example when trying to import the 2015 statistics):
>>
>> /opt/dspace/bin/dspace solr-import-statistics -i statistics-2015
>> Exception: Error from server at
>> http://localhost:8983/solr/statistics-2015: Expected mime type
>> application/octet-stream but got text/html. 
>> 
>> 
>> Error 404 Not Found
>> 
>> HTTP ERROR 404 Not Found
>> 
>> URI:/solr/statistics-2015/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-2015:
>> Expected mime type application/octet-stream but got text/html. 
>> 
>> 
>> Error 404 Not Found
>> 
>> HTTP ERROR 404 Not Found
>> 
>> URI:/solr/statistics-2015/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:77)
>> at
>> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.base/java.lang.reflect.Method.invoke(Method.java:568)
>> at
>> org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:277)
>> at
>> org.dspace.app.launcher.ScriptLauncher.handleScript(ScriptLauncher.java:133)
>> at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:98)
>>
>> Presumably this is due 

[dspace-tech] Re: Angular "dspace-ui-deploy" directory large "core.*" files

['Tim Donohue' via DSpace Technical Support]

Hi,

Those "core.*" files are not being created by DSpace.   DSpace never 
writes/creates new files to that folder once it is running.

It's likely those are memory dumps created by Linux.  It sounds like some 
process (maybe Node.js, or whatever else you are using the run the DSpace 
UI?) is running out of memory and/or crashing frequently. That is likely 
what is creating these "core.*" files.  See this StackOverflow for 
example: https://stackoverflow.com/a/20530587/3750035

Tim

On Thursday, April 13, 2023 at 1:01:26 PM UTC-5 bwe...@gmail.com wrote:

> Forgot I'm using dspace-angular 7.5
>
> On Thursday, April 13, 2023 at 12:59:38 PM UTC-5 hb wooley wrote:
>
>> Hoping someone can help.
>> Under the Angular "dspace-ui-deploy" directory where you copy the Angular 
>> "dist" folder, I'm seeing large core.* files. These (binary) files keep 
>> growing in this directory, can someone tell me what these files are for and 
>> can the number of them be limited, since they can fill up a drive if not 
>> monitored?
>> Example:
>> 2.3G Mar 24 15:28 core.18471
>> 2.3G Mar 25 00:58 core.23446
>> 2.3G Mar 25 21:18 core.10618
>> 2.3G Mar 26 22:59 core.3294
>> 2.3G Mar 28 01:15 core.19507
>> 2.3G Mar 28 12:49 core.16889
>> 2.4G Mar 30 12:30 core.3287
>> 2.3G Apr  1 00:25 core.4652
>> 2.3G Apr  3 14:10 core.7601
>> 2.3G Apr  5 00:59 core.28903
>> 2.3G Apr  5 19:18 core.12439
>> 2.3G Apr  7 09:17 core.9281
>> 2.3G Apr  8 00:19 core.6379
>> 2.3G Apr  8 00:49 core.7008
>> 2.3G Apr  8 12:25 core.18488
>> 2.3G Apr  9 12:23 core.32223
>> 2.3G Apr 10 12:23 core.1507
>> 2.3G Apr 11 20:29 core.3029
>> 2.3G Apr 13 12:22 core.6437
>>
>> Thank you -
>>
>

-- 
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/9ce2884d-2ff8-430c-bf32-484b971dc20dn%40googlegroups.com.

[dspace-tech] Permanent URI for this community http://localhost:4000/handle/...

[Costantino , Fernán]

 

Hi, I was trying to understand how to fix this. 

"Permanent URI for this community" link to
http://localhost:4000/handle/... instead of dspace.ui.url (dspace.cfg) 

There are some discussions/issues on github (for example:
https://github.com/DSpace/dspace-angular/issues/887 ), but is difficult
to me to follow the thread. Can someone explain the procedure to solve
it? It seems that I need to modify some code? Thanks. 
-- 

COSTANTINO, FERNÁN
División Nuevas Tecnologías
Biblioteca Central Francisco P. Moreno
Universidad Nacional del Comahue
Santa Fe y Leloir (Q8300) Neuquén Cap.- Tel 54(0299)4490398
 

-- 
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/1cd0c644401bdfec9725d3dd116d2bdb%40biblioteca.uncoma.edu.ar.

[dspace-tech] DSpace Development Fund - Call for Contributions

[Maureen P. Walsh]

Since the launch of the DSpace Development Fund

in
March 2022, members of the worldwide DSpace community have contributed over
$140,000 to support funded development for DSpace.

These generous contributions have directly supported software development of
key features of DSpace 7

prioritized by the DSpace community.

As we look toward planned releases in 2023, we need the DSpace Community’s
help to bring DSpace 7 over the finish line.  Funds contributed to the
DSpace Development Fund in the coming months will fuel development at our
current pace and help DSpace 7 achieve feature parity with version 6. Our
goal is to raise $100,000 to do that.

You and your organization can help by adding your contribution to the
DSpace Development Fund.

   -

   Does your organization have a fiscal year ending June 30th and have
   money left in the budget?  Please consider using those funds to fuel DSpace
   development!
   -

   Is your organization not yet a contributing member of DSpace
   . Please join us!
   -

   Would your organization like to contribute to DSpace development in some
   other way? Contact us to discuss some options.

If you would like to know more and/or contribute to the DSpace Development
Fund, please contact us at dspacedonati...@lyrasis.org.  You can also visit
the DSpace wiki

for
more information about the DSpace Development Fund and see a list of
institutions that have already contributed.

DSpace continues to grow and evolve to sustain open repositories because of
generous contributions of time and resources by the global DSpace
community. Thank you for your continued support.

Maureen Walsh

Chair, DSpace Leadership and Steering Groups

on behalf of DSpace Governance


Maureen P. Walsh
Associate Professor
Scholarly Sharing Strategist
The Ohio State University
University Libraries
walsh@osu.edu
Pronouns: she/her

-- 
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/CAKj8zsXvNYu%3D3B-zmeoeD6fsBvXRHuXuoa7bQm8Tqq60Npcd2w%40mail.gmail.com.

[dspace-tech] Re: Angular "dspace-ui-deploy" directory large "core.*" files

[hb wooley]

Forgot I'm using dspace-angular 7.5

On Thursday, April 13, 2023 at 12:59:38 PM UTC-5 hb wooley wrote:

> Hoping someone can help.
> Under the Angular "dspace-ui-deploy" directory where you copy the Angular 
> "dist" folder, I'm seeing large core.* files. These (binary) files keep 
> growing in this directory, can someone tell me what these files are for and 
> can the number of them be limited, since they can fill up a drive if not 
> monitored?
> Example:
> 2.3G Mar 24 15:28 core.18471
> 2.3G Mar 25 00:58 core.23446
> 2.3G Mar 25 21:18 core.10618
> 2.3G Mar 26 22:59 core.3294
> 2.3G Mar 28 01:15 core.19507
> 2.3G Mar 28 12:49 core.16889
> 2.4G Mar 30 12:30 core.3287
> 2.3G Apr  1 00:25 core.4652
> 2.3G Apr  3 14:10 core.7601
> 2.3G Apr  5 00:59 core.28903
> 2.3G Apr  5 19:18 core.12439
> 2.3G Apr  7 09:17 core.9281
> 2.3G Apr  8 00:19 core.6379
> 2.3G Apr  8 00:49 core.7008
> 2.3G Apr  8 12:25 core.18488
> 2.3G Apr  9 12:23 core.32223
> 2.3G Apr 10 12:23 core.1507
> 2.3G Apr 11 20:29 core.3029
> 2.3G Apr 13 12:22 core.6437
>
> Thank you -
>

-- 
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/b551126b-6890-4139-b683-f6ce3fc6ebben%40googlegroups.com.

[dspace-tech] Angular "dspace-ui-deploy" directory large "core.*" files

[hb wooley]

Hoping someone can help.
Under the Angular "dspace-ui-deploy" directory where you copy the Angular 
"dist" folder, I'm seeing large core.* files. These (binary) files keep 
growing in this directory, can someone tell me what these files are for and 
can the number of them be limited, since they can fill up a drive if not 
monitored?
Example:
2.3G Mar 24 15:28 core.18471
2.3G Mar 25 00:58 core.23446
2.3G Mar 25 21:18 core.10618
2.3G Mar 26 22:59 core.3294
2.3G Mar 28 01:15 core.19507
2.3G Mar 28 12:49 core.16889
2.4G Mar 30 12:30 core.3287
2.3G Apr  1 00:25 core.4652
2.3G Apr  3 14:10 core.7601
2.3G Apr  5 00:59 core.28903
2.3G Apr  5 19:18 core.12439
2.3G Apr  7 09:17 core.9281
2.3G Apr  8 00:19 core.6379
2.3G Apr  8 00:49 core.7008
2.3G Apr  8 12:25 core.18488
2.3G Apr  9 12:23 core.32223
2.3G Apr 10 12:23 core.1507
2.3G Apr 11 20:29 core.3029
2.3G Apr 13 12:22 core.6437

Thank you -

-- 
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/91c5a47d-bffd-4494-a786-12863033c50en%40googlegroups.com.

[dspace-tech] Re: Dspace 7 cannot upload file

[DSpace Technical Support]

Please see our troubleshooting guide for information about how to locate 
specific error messages (in the UI or in the backend).  Unfortunately, 
without a specific error message, it's impossible to provide accurate 
advice.  It could be the frontend is having issues communicating with the 
backend. It could be the file is too large.  It could also be that you are 
out of storage.  It could be some other problem altogether.

The only way to know what is wrong is to find the detailed error.

https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

Once you find the detailed error, feel free to send it to this mailing list 
for more help.

Tim

On Tuesday, April 11, 2023 at 7:05:22 PM UTC-5 yus...@utm.my wrote:

> Hi,
>
> I have successfully installed Dspace 7 and have started using it. Before 
> this I managed to upload the file but suddenly the file cannot be uploaded. 
> After looking in the log file. no errors found. Please help..URGENT. 
>
>
> DISCLAIMER: The information in this e-mail and any attachment(s) 
> transmitted with it ("Message") is intended only for the use of the 
> intended recipient(s) and may contain confidential or privileged 
> information. UTM are not responsible for any unauthorised changes made to 
> the information or for the effect of such changes. You are hereby notified 
> that any action in reliance upon, or any review, retransmission, 
> dissemination, distribution, printing or copying of this Message or any 
> part thereof by anyone other than the intended recipient(s) is strictly 
> prohibited. Any opinions, conclusions and other information in this Message 
> that do not relate to the official business of UTM shall be understood as 
> neither given nor endorsed by UTM. UTM shall not be liable for loss or 
> damage caused by viruses transmitted by this Message.
>

-- 
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/0e13b24d-63c8-4033-83cd-0ba5da14fa71n%40googlegroups.com.

[dspace-tech] Re: limited bitstream permission and Mirador

['Tim Donohue' via DSpace Technical Support]

Hi all,

This is a known issue.  Currently, Mirador in DSpace isn't able to view 
restricted content, as it cannot pass the authentication info properly back 
to DSpace: https://github.com/DSpace/dspace-angular/issues/1435

There's been ongoing work on this, but it has hit a number of complications 
(as it's not simple): https://github.com/DSpace/dspace-angular/pull/1436

I know Michael Spalti (who created that PR) has been interested in this for 
some time.  There are others who would also like to have this feature... 
it's just a matter of finding a solution that can work for everyone & that 
can be added to out-of-the-box DSpace.

So, basically, we don't have a solution yet here. But, I'm hopeful that 
someone will figure this out & share their approach (whether in code or in 
a specific configuration) so that we can make it available to everyone. If 
you'd like to help, you might get in touch via that PR by adding a comment 
or similar.

Tim



On Tuesday, April 11, 2023 at 2:12:34 AM UTC-5 Evelin Bányai wrote:

> Thanks. Apparently we have Mirador 3, we will try to figure out how the 
> authentication works for Mirador.
>
> Best regards,
> Evelin
>
> west...@umd.edu a következőt írta (2023. április 8., szombat, 17:09:57 
> UTC+2):
>
>> Which version of Mirador? Mirador 3 supports IIIf Authentication (
>> https://iiif.io/api/auth/1.0/), which seems like the way to do this. 
>> Caveat: we have not implemented this ourselves.
>>
>> Josh Westgard
>> University of Maryland College Park
>>
>> On Friday, April 7, 2023 at 6:07:13 PM UTC-4 Chris Clawson wrote:
>>
>>> I have been asked to do this as well. Does anybody know a method?
>>>
>>> On Monday, April 3, 2023 at 7:23:00 AM UTC-4 Evelin Bányai wrote:
>>>
 Hello,

 There are certain items we would like to have with withdrawn_read 
 bitstream permission so the users should ask for permission to download 
 the 
 full picture. However, if we setup up the item with such permission the 
 built-in Mirador viewer won't show anything.

 Is there a way to set up such configuration where the file download is 
 limited but the viewer able to show the image? I have my doubts, but it's 
 worth a try to ask.

 We have version 7.2.1.

 Thanks!
 Evelin

>>>

-- 
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/c6d4782f-8ccf-4d10-9a4d-55dbdffe949en%40googlegroups.com.

[dspace-tech] Re: Password complexity and max failures attempts

['Tim Donohue' via DSpace Technical Support]

Hi,

In DSpace 7, you can manage password complexity rules in a configuration.  
It's controlled by a regex pattern defined here:
https://github.com/DSpace/DSpace/blob/main/dspace/config/modules/authentication-password.cfg#L51

Some examples of different patterns are given in the comments of that 
config file.

At this time though there is no "maximum failure" attempt rules for the 
default password system.  I do agree this would be useful enhancement 
though... so, you are welcome to create a bug ticket regarding this & we'll 
see if we can locate a volunteer interested in implementing 
it. https://github.com/DSpace/DSpace/issues

Tim

On Thursday, April 6, 2023 at 6:20:27 AM UTC-5 Brandon Sauvenière 
(Brandysve) wrote:

> Hello,
>
> Is it possible to manage the password complexity when user create a 
> password? (ex : min 14 chars with uppercase, lowercase, numbers and special 
> chars). 
>
> It there a maximal failures attempts? We're planning to use dspace for our 
> target with +/- 15000 users. We want to be sure that it is safe against 
> attacks.
>
> It is external users so we don't use LDAP, shibboleth, etc...
>
> Thank you :)
>

-- 
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/0f0a2669-55c4-49cc-aee7-7a51e12be664n%40googlegroups.com.

Re: [dspace-tech] Set up Dspace 7.2

[Mark H. Wood]

On Wed, Apr 12, 2023 at 08:19:16AM -0700, LSBU wrote:
> Hello, I would like to know some parameters for my Dspace 7.2: 

That is quite outdated now.  You should consider upgrading to 7.5 at
your earliest convenience.

> 1- How to create a user group on the terminal ?

That is not implemented.

> 2- how to add a user on the terminal ?

'bin/dspace user --add --help' will show you the options.  'bin/dspace
user --help' will show you other things you can do with user accounts
from the command line.

The 'user' command is documented at
https://wiki.lyrasis.org/display/DSDOC7x/Managing+User+Accounts

The command line tools are summarized at
https://wiki.lyrasis.org/display/DSDOC7x/Command+Line+Operations

> 3- how to import users from the terminal ?

You can make a script of 'add' commands and run it with 'bin/dspace read'.

> 4- what are the services to start after restarting the server to make 
> Dspace functional ?

You will need your Servlet container (usually Tomcat), Solr, and the
DBMS (usually PostgreSQL).  If you have registered with the Handle
Service then you will also want to run the local Handle resolver.

> 5- how to automate these services so that they start automatically at 
> server startup ?

That depends on your operating system.  What are you running?

> 6- how to improve response times if we perform a search from the portal.5 ?

I don't understand "portal.5".

> 7- What are the data and configuration files to backup so that in case of a 
> problem, we can restore our database?

You need to back up the assetstore directories and a dump of the
database.

The DBMS has tools to dump and restore databases, and this is how you
should back them up.  It is nearly impossible to get a consistent
backup of most database products' content by saving their raw files.

The assetstore can be backed up as-is.

You will also want to back up 'config/' and its subdirectories.

You should also consider
https://wiki.lyrasis.org/display/DSDOC7x/AIP+Backup+and+Restore

-- 
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/ZDfs9i1Q6l1o%2BIMh%40IUPUI.Edu.


signature.asc
Description: PGP signature