[dspace-tech] DSpace and Date Range Queries

['Maruan Sahyoun' via DSpace Technical Support]

Dear All,

I have a date range field dc.coverage.temporal which leads to different 
results when being searched for using the DSpace Serach Field and a direct 
Solr query

dc.identifier:19900816_lh_lu_422 && dc.coverage.temporal:[1991 TO 1992]
in the search fields doesn't find the entry 

where
curl -g 
"http://localhost:8983/solr/search/select?q=dc.identifier:19900816_lh_lu_422&:%5B1991%20TO%201992%5D;
against Solr does find it. 

The dc.coverage.temporal field has "[1990 TO 1995]"

Changing the DSpace search to
dc.identifier:19900816_lh_lu_422 && dc.coverage.temporal:[1990 TO 1992]
i.e. using the lower bounds as the start does find the enry.

Is there something I'm doing/expecting wrong?

With kind regards
Maruan

-- 
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/f349ff40-fbad-4dc0-9309-9493ba75a42cn%40googlegroups.com.

[dspace-tech] Re: DSpace 7.6.1 How to make search work with AND operator instead of OR

['Maruan Sahyoun' via DSpace Technical Support]

Did you try putting the string in quotes?

BR
Maruan

Matthias Letsch schrieb am Freitag, 12. April 2024 um 16:18:34 UTC+2:

> Just for the sake of completeness: Unfortunately, our search does not work 
> as documented here: 
> https://wiki.lyrasis.org/display/DSDOC7x/Search+-+Advanced
>
> It says here that "Basic searching" corresponds to an AND search, but 
> unfortunately this is not the case with us...
>
> Matthias Letsch schrieb am Freitag, 12. April 2024 um 16:10:58 UTC+2:
>
>> Hello there,
>>
>> Our quick search form on the homepage and in the navigation bar ist 
>> working with a boolean OR operator by default. For example, if I enter the 
>> string "Adaptation of model organisms", I get a hit list with over 700 hits 
>> because every single entry is listed that contains any of the words 
>> "adaptation" OR "of" (!) OR "model" OR "organisms" in any indexed metadata 
>> field. I know that there is a publication with a title beginnig exactly 
>> with this string, but that hit is not at the top, but hidden somewhere in 
>> the middle of a list of otherwise not relevant hits.
>>
>> I personally don't find this useful and I don't know who does. When I 
>> enter a bunch of words in a "quick search" form, I want exactly the results 
>> that contain ALL the terms entered - the results of a search with an AND 
>> operator. An OR search should only be available, if at all, as an advanced 
>> search option that the user consciously selects.
>>
>> So where can I change the behavior of the search and set it accordingly?
>>
>> Thank you and kind regards
>> Matthias
>>
>

-- 
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/dc615cc1-51ae-41ec-be8c-8ab7fbb7942en%40googlegroups.com.

[dspace-tech] Re: Java heap space

['Maruan Sahyoun' via DSpace Technical Support]

Hi,

this is documented here 
https://wiki.lyrasis.org/display/DSDOC7x/Performance+Tuning+DSpace#PerformanceTuningDSpace-GivetheCommandLineToolsMoreMemory

With kind regards
Maruan Sahyoun
FileAffairs GmbH

Alex B schrieb am Donnerstag, 4. April 2024 um 12:24:15 UTC+2:

> Dear colleagues, in the process of creation AIP of dspace - 
>
> /dspace/bin/dspace packager -d -a -t AIP -e ro...@root.com -i 123456789/0
>
> got the following error:
>
> Exception in thread "Thread-0" java.lang.OutOfMemoryError: Java heap space
>
> How can I fix this error?
>
> Best regards,
> Alex
>

-- 
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/33bc1c52-6782-4751-9e14-797c3533df25n%40googlegroups.com.

[dspace-tech] Re: High CPU usage in DSpace 7.6 leading to server issues, lots of errors/examples (crossposted from Slack)

['Maruan Sahyoun' via DSpace Technical Support]

Dear Carolyn,

not directly answering your question but we are running (a possibly smaller 
instance of DSpace for a non insitutonal site) without PM2 but with node.js 
directly. With the amount of traffic you are having you might want to give 
it a try to rule out PM2 and it's handling as a souce of error. With our 
install we are not getting e.g.  
*ERR_HTTP_HEADERS_SENT *

BR
Maruan Sahyoun
FileAffairs GmbH
Carolyn Sullivan schrieb am Dienstag, 5. März 2024 um 11:30:15 UTC+1:

> Hello all,
>
> As you might have seen if you frequent the Technical Support channel in 
> the DSpace Slack 
> , 
> we've been encountering high CPU usage in DSpace 7.6 leading to decreased 
> performance (ie. site unavailability) and we've been having a lot of 
> errors.  We're not entirely sure which errors may be the significant ones 
> relating to our performance challenges, and would welcome any input from 
> the community to help us improve our site issues.  Also, if you're 
> encountering similar issues, please do let us know--maybe we're all having 
> the same problems and can solve these collaboratively.  Thanks already to 
> Tim Donoghue and Mark Wood for their suggestions in the DSpace Slack!  I've 
> aggregated the responses we've already received on these issues here to 
> enable us to keep track of suggestions.
>
> So, a summary of our issues:  We've set up our server following best 
> practices in the Performance Tuning documentation 
> .  We 
> run everything on a single server with 4 CPU and 12 GB of RAM, which was 
> the configuration that worked for our previous version of DSpace (6.3).  
> Initially, we had pm2 configured in cluster mode with max instances and 
> max_memory_restart: 500M. With this configuration, the node instances kept 
> restarting ~every minute and seemed to be monopolizing the CPUs, and 
> starving the other components.  Since then, we have since tuned it down to 
> 3 instances, ie:
>
> {
> "apps": [
> {
>"name": "dspace-ui",
>"cwd": "/var/dspace-frontend/",
>"script": "dist/server/main.js",
>"instances": "3",
>"exec_mode": "cluster",
>"timestamp": "-MM-DD HH:mm Z",
>"out_file": "log/dspace-ui.log",
>"error_file": "log/dspace-ui_error.log",
>"merge_logs": true,
>"env": {
>   "NODE_ENV": "production",
>   "NODE_EXTRA_CA_CERTS": "/etc/ssl/certs/rootCA2.crt"
>},
>"max_memory_restart": "1500M",
>"node_args": "--max_old_space_size=4096"
> }
> ]
> }
>
> A review of process with top shows very active node instances despite low 
> traffic (~ 1 request/second):
>
> Tasks: 289 total,   5 running, 284 sleeping,   0 stopped,   0 zombie
> %Cpu(s): 93.9 us,  3.0 sy,  0.0 ni,  3.0 id,  0.0 wa,  0.0 hi,  0.0 si, 
>  0.0 st
> MiB Mem :  11965.2 total,440.4 free,  10901.1 used,623.8 buff/cache
> MiB Swap:  0.0 total,  0.0 free,  0.0 used.613.9 avail Mem
> PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ 
> COMMAND
> 1504803 dspace20   0 2328180   1.5g  13936 R 100.0  12.5  10:53.08 
> node /v+
> 1506783 dspace20   0 2620092   1.7g  14024 R  93.8  14.8   9:44.49 
> node /v+
> 1506913 dspace20   0 1383380 586472  14180 R  93.8   4.8   4:57.11 
> node /v+
> 1508040 dspace20   0  733380 141452  36952 R  75.0   1.2   0:00.77 
> node /v+
> 781 root  20   0  237020   2536944 S   6.2   0.0   9:41.79 
> vmtoolsd
>   1 root  20   0  171488   7176   2492 S   0.0   0.1   0:44.04 
> systemd
>
> Our cache settings are set as follows:
> # Caching settings
> cache:
> ...
>   serverSide:
> debug: false
> botCache:
>   max: 1000
>   timeToLive: 8640 # 1 day
>   allowStale: true
> anonymousCache:
>   max: 1000
>   timeToLive: 1 # 10 seconds
>   allowStale: true
>
> *The main question of our systems analyst (Francois Malric): Is this level 
> of constantly high CPU usage is normal due to node.js?  Or is it likely 
> that our DSpace is displaying poor performance due to underlying issues?*
>
> Here are some examples of the errors we've seen:
>
> (1) From our DSpace Logs:  According to this, we don't have that much 
> traffic (HTTP 0.96 requests/minute), which would likely be higher if bot 
> traffic was the issue.  Nota bene, our pm2 monitor likely has a bug as it's 
> showing the units as req/min; should be req/sec.
>
> lq Process List klqq  dspace-ui Logs 
>  k
> x[ 1] dspace-ui Mem: 824 MB xx dspace-ui > The response for '
> https://ruor.uottawa.ca/server/api/core/items/d2d3c  x
> x[ 2] dspace-ui Mem: 316 MB xx dspace-ui > 1 rules skipped due to 
> selector errors:  

[dspace-tech] Re: item with many files not working.

['Maruan Sahyoun' via DSpace Technical Support]

Not directly answering your question but you could tune your nginx settings 
e.g.

proxy_busy_buffers_size 512k;
proxy_buffers 4 512k;
proxy_buffer_size 256k;

or disable buffering 

proxy_buffering off;

which I wouldn't recommend for performance reasons.

BR
Maruan Sahyoun
FileAffairs GmbH

bens...@gmail.com schrieb am Freitag, 1. März 2024 um 01:43:23 UTC+1:

> In dspace 7.6.1 I had an item with 25 files in it.
>
> after an image was generated for each pdf the page would not load. 
>
> **pm2 is behind nginx and the nginx log says:
>
> 2024/02/29 16:00:50 [error] 25186#0: *3824 upstream sent too big header 
> while reading response header from upstream,
>  client: 142.104.201.218, server: dspace.library.uvic.ca, request: "GET 
> /items/b94e7193-a7dd-42ef-b551-5f31808291fb HTTP/1.1",
>  upstream: "http://[::1]:4000/items/b94e7193-a7dd-42ef-b551-5f31808291fb;, 
> host: "dspace.library.uvic.ca"
>
> when I removed all the generated images it worked again.
>
> My question: Is there a best practice to limit the number of files in an 
> item?
>
> Thanks,
> Ben
>

-- 
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/f384b729-0206-4fa6-9609-d8982ef2ca7bn%40googlegroups.com.

[dspace-tech] Re: Unable to activate WRITE permission to eperson

['Maruan Sahyoun' via DSpace Technical Support]

Permissions exist at item level but are inherited when created new from the 
collection level. So when an item did exist before the the eperson has been 
added it might not have a WRITE permission.

Bulk Access Management (both at UI level and from the console) allow you to 
change permissons for multiple existing items if needed.

BR
Maruan
FileAffairs GmbH

xan...@gmail.com schrieb am Freitag, 9. Februar 2024 um 08:49:12 UTC+1:

> Hi,
>
> Recently installed DSpace 7.6 on Ubuntu 22.04.3. Created communities, 
> collection and submitted items by new eperson. I have added new 
> authorization policy for eperson with WRITE permission in Collection 
> level.  But the added eperson is not able to edit the submitted item. Only 
> Admin user can edit the items.  However, if I add Item level WRITE 
> permission to eperson, then it is working. 
>
> Is it the correct way or not possible to do in Collection level ?
> Please, if anyone has advice for me, I would appreciate the help. 
>
> Regards,
> sk deka, 
>

-- 
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/ad67609f-addf-40f5-9967-03324226f272n%40googlegroups.com.

[dspace-tech] Re: Subject category control

['Maruan Sahyoun' via DSpace Technical Support]

Hi,

this is documented in 
https://wiki.lyrasis.org/display/DSDOC7x/Authority+Control+of+Metadata+Values

BR
Maruan
FileAffairs GmbH

Lewatle Johannes Phaladi schrieb am Donnerstag, 8. Februar 2024 um 15:16:48 
UTC+1:

> Dear DSpace Tech,
>
> Where can one control subject category on DSpace 7.6, the folowing appears 
> on my frontend without us choosing which subject to appear etc. Please help 
> :
>
>
> [image: image_2024-02-08_161516579.png]
>
> Regards,
> Lewatle
>

-- 
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/e70430ae-8c78-41d5-83fe-fe9d95791054n%40googlegroups.com.

[dspace-tech] Re: Problems with SOLR

['Maruan Sahyoun' via DSpace Technical Support]

Hi Gladys,

can you share your init.d script?

BR
Maruan

Gladys Vanesa Fernandez schrieb am Dienstag, 30. Januar 2024 um 15:40:29 
UTC+1:

> Hi Maruan, from the directory, Solr is running correctly 
>
> El martes, 30 de enero de 2024 a las 11:31:20 UTC-3, Maruan Sahyoun 
> escribió:
>
>> Hello Gladys,
>>
>> did you try starting SOLR manually from it's bin directory? Does that 
>> work without any issues?
>>
>> With kind regards
>>
>> Maruan
>> FileAffairs GmbH
>>
>> Gladys Vanesa Fernandez schrieb am Dienstag, 30. Januar 2024 um 13:58:42 
>> UTC+1:
>>
>>> Hello everyone, I'm having an issue with Solr that stopped working on 
>>> its own. I've already performed various processes, such as uninstalling and 
>>> reinstalling it, changing ownership, etc., but it always throws the same 
>>> error:
>>> solr.service - LSB: Controls Apache Solr as a Service
>>>  Loaded: loaded (/etc/init.d/solr; generated)
>>>  Active: failed (Result: exit-code) since Tue 2024-01-30 09:46:17 
>>> -03; 5s ago
>>>Docs: man:systemd-sysv-generator(8)
>>> Process: 996403 ExecStart=/etc/init.d/solr start (code=exited, 
>>> status=1/FAILURE)
>>> CPU: 4ms
>>>
>>> Jan 30 09:46:16 DSpace-SDC systemd[1]: Starting LSB: Controls Apache 
>>> Solr as a Service...
>>> Jan 30 09:46:16 DSpace-SDC su[996405]: (to solr) root on none
>>> Jan 30 09:46:16 DSpace-SDC su[996405]: pam_unix(su-l:session): session 
>>> opened for user solr(uid=122) by (uid=0)
>>> Jan 30 09:46:17 DSpace-SDC su[996405]: pam_unix(su-l:session): session 
>>> closed for user solr
>>> Jan 30 09:46:17 DSpace-SDC systemd[1]: solr.service: Control process 
>>> exited, code=exited, status=1/FAILURE
>>> Jan 30 09:46:17 DSpace-SDC systemd[1]: solr.service: Failed with result 
>>> 'exit-code'.
>>> Jan 30 09:46:17 DSpace-SDC systemd[1]: Failed to start LSB: Controls 
>>> Apache Solr as a Service.
>>>
>>> In dont have more information in logs files
>>> I use Dspace 7.6.1 on Ubuntu 22.04
>>>
>>> Thanks!
>>>
>>

-- 
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/888b0054-ea96-445a-8436-228214051ca5n%40googlegroups.com.

[dspace-tech] Re: Problems with SOLR

['Maruan Sahyoun' via DSpace Technical Support]

Hello Gladys,

did you try starting SOLR manually from it's bin directory? Does that work 
without any issues?

With kind regards

Maruan
FileAffairs GmbH

Gladys Vanesa Fernandez schrieb am Dienstag, 30. Januar 2024 um 13:58:42 
UTC+1:

> Hello everyone, I'm having an issue with Solr that stopped working on its 
> own. I've already performed various processes, such as uninstalling and 
> reinstalling it, changing ownership, etc., but it always throws the same 
> error:
> solr.service - LSB: Controls Apache Solr as a Service
>  Loaded: loaded (/etc/init.d/solr; generated)
>  Active: failed (Result: exit-code) since Tue 2024-01-30 09:46:17 -03; 
> 5s ago
>Docs: man:systemd-sysv-generator(8)
> Process: 996403 ExecStart=/etc/init.d/solr start (code=exited, 
> status=1/FAILURE)
> CPU: 4ms
>
> Jan 30 09:46:16 DSpace-SDC systemd[1]: Starting LSB: Controls Apache Solr 
> as a Service...
> Jan 30 09:46:16 DSpace-SDC su[996405]: (to solr) root on none
> Jan 30 09:46:16 DSpace-SDC su[996405]: pam_unix(su-l:session): session 
> opened for user solr(uid=122) by (uid=0)
> Jan 30 09:46:17 DSpace-SDC su[996405]: pam_unix(su-l:session): session 
> closed for user solr
> Jan 30 09:46:17 DSpace-SDC systemd[1]: solr.service: Control process 
> exited, code=exited, status=1/FAILURE
> Jan 30 09:46:17 DSpace-SDC systemd[1]: solr.service: Failed with result 
> 'exit-code'.
> Jan 30 09:46:17 DSpace-SDC systemd[1]: Failed to start LSB: Controls 
> Apache Solr as a Service.
>
> In dont have more information in logs files
> I use Dspace 7.6.1 on Ubuntu 22.04
>
> Thanks!
>

-- 
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/4d06fbdb-64af-45da-8fe9-753ee99416c1n%40googlegroups.com.

[dspace-tech] Re: SLOR error string field too large

['Maruan Sahyoun' via DSpace Technical Support]

I'm wondering if the content is correct. Looks like you are trying to index 
content larger than 32766 but that's coming from the field bi_2_dis_prefix. 
Are you sure that the content in that field is correct.

To handle content larger than 32766 you need to change the field type in 
the Solr schema. It looks like you are using a string type to hold the data 
but string is limited in length. You can change to 'text' for example which 
allows to handle more data.

BR
Maruan
FileAffairs GmbH  


Jack OE schrieb am Dienstag, 23. Januar 2024 um 08:09:09 UTC+1:

> Hi all,
>
> We've been encountering this error with SOLR in the past few days and I am 
> wondering if anyone has any a solution for it, any help is greatly 
> appreciated!
>
> Remote error message: Exception writing document id 
> Item-1739ff68-6dff-46ca-ad71-b8803a2a9137 to the index; possible analysis 
> error: Document contains at least one immense term in 
> field="bi_2_dis_prefix" (whose UTF8 encoding is longer than the max length 
> 32766), all of which were skipped.  Please correct the analyzer to not 
> produce such terms.  The prefix of the first immense term is: '[98, 114, 
> 111, 119, 110, 44, 32, 112, 46, 59, 122, 104, 111, 117, 44, 32, 121, 46, 
> 59, 116, 97, 110, 44, 32, 97, 46, 45, 99, 46, 59]...', original message: 
> bytes can be at most 32766 in length; got 37865. Perhaps the document has 
> an indexed string field (solr.StrField) which is too large
> at 
> org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:681)
> 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.SolrClient.add(SolrClient.java:177)
> at org.apache.solr.client.solrj.SolrClient.add(SolrClient.java:138)
> at org.apache.solr.client.solrj.SolrClient.add(SolrClient.java:156)
> at 
> org.dspace.discovery.indexobject.IndexFactoryImpl.writeDocument(IndexFactoryImpl.java:151)
> at 
> org.dspace.discovery.indexobject.ItemIndexFactoryImpl.writeDocument(ItemIndexFactoryImpl.java:752)
> at 
> org.dspace.discovery.indexobject.ItemIndexFactoryImpl.writeDocument(ItemIndexFactoryImpl.java:81)
> at 
> org.dspace.discovery.SolrServiceImpl.update(SolrServiceImpl.java:186)
> at 
> org.dspace.discovery.SolrServiceImpl.indexContent(SolrServiceImpl.java:175)
> at 
> org.dspace.discovery.SolrServiceImpl.updateIndex(SolrServiceImpl.java:365)
> at 
> org.dspace.discovery.SolrServiceImpl.updateIndex(SolrServiceImpl.java:352)
> at 
> org.dspace.discovery.SolrServiceImpl.createIndex(SolrServiceImpl.java:320)
> at 
> org.dspace.discovery.IndexClient.internalRun(IndexClient.java:120)
> at org.dspace.scripts.DSpaceRunnable.run(DSpaceRunnable.java:150)
> at 
> org.dspace.app.launcher.ScriptLauncher.executeScript(ScriptLauncher.java:174)
> at 
> org.dspace.app.launcher.ScriptLauncher.handleScript(ScriptLauncher.java:151)
> at 
> org.dspace.app.launcher.ScriptLauncher.handleScript(ScriptLauncher.java:125)
> at 
> org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:100)
>

-- 
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/6beb7b75-b9c8-4bf7-99aa-842f24c3c03en%40googlegroups.com.

[dspace-tech] Re: Error IP vs Domain Name (DNS)

['Maruan Sahyoun' via DSpace Technical Support]

is there a proxy in place which forwards http to https when accessing via 
domain name instead of IP?

Kind regards
Maruan
FileAffairs GmbH

Michel Montenegro schrieb am Mittwoch, 17. Januar 2024 um 23:14:51 UTC+1:

> When we configure DPSPACE via IP (xxx.xxx.xxx.xxx) the system works 
> perfectly!
>
> When we configure everything to use DNS (www.mydomain) the Frontend does 
> not access the Backend.
>
> When analyzing we see that the Frontend looks for port 443, *but we 
> configured port 80* in its configuration files. When we use IP the system 
> looks for port 80 as it is in the configuration files and it works 
> perfectly.
> [image: image.png]
>
> What could cause this type of problem?
>
> -- 
> Atenciosamente, 
> *Michel Pinheiro Montenegro*
> - *Bacharel* em Sistema de Informação
> - [Lato Sensu] *Especialista* em Engenharia de Sistemas
> - [Stricto Sensu] *Mestre* em Ciência da Computação
> - [Stricto Sensu] *Doutorando* em Ciência da Computação
>
> E-mail/Gtalk: michel.m...@gmail.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/2633c765-4e07-4250-a4c5-b1229edf77e7n%40googlegroups.com.

[dspace-tech] Re: HELP - dspace database migration failed

['Maruan Sahyoun' via DSpace Technical Support]

Hello Dan,

looks like the DB user doesn't have the proper rights on the DB. Could you 
check that.

BR
Maruan
FileAffairs GmbH

Dan Guillang schrieb am Mittwoch, 3. Januar 2024 um 20:21:46 UTC+1:

> I just started and needed dspace for thesis purposes and after series of 
> installation and steps i able to accomplish it based on the guidelines.
>
> but in the migration of database step, I failed as my database is not on 
> auto-initialize and in state of PENDING.
>
> here is the result of ./dspace database info
>
> [image: dspace database info.png]
>
> and this is the error message of the command line ./dspace database 
> migration
>
> [image: dspace database migrate.png]
>
> i hope will be able to help me, more power to you guys and happy new year!
>

-- 
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/fbbb71fe-5ce2-47a1-bd13-ae40a0c0a0f3n%40googlegroups.com.

[dspace-tech] Re: Error in migrating server using AIP method

['Maruan Sahyoun' via DSpace Technical Support]

Although not a direct answer to your question youl could dump the existing 
DB and import the dump into the new DB for metadata etc and copy the 
assetstore subdirectory to you new install. Worked very smoothly for me and 
was also very fast compared to importing from AIP.

BR
Maruan

Salony Permanand schrieb am Montag, 18. Dezember 2023 um 17:36:20 UTC+1:

>
> Hello All,
>
> I want to migrate a server which is in DSpace 7.4 to DSpace 7.6
>
> For this I used AIP method where I took backup from on server and tried to 
> restore it in new server
>
> While performing restore task ,
> I am getting below error.
>
> Attaching scrnshot of the error. 
>
> Please help to solve asap  
>
> Thanks
>
> Salony Permanand
> *Mob: 7275838206 <(727)%20583-8206>*
>

-- 
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/eb14839d-5a3d-48ad-9b7c-a07c2fcb96c9n%40googlegroups.com.

[dspace-tech] Re: Bulk access management doesn't remove access conditions

['Maruan Sahyoun' via DSpace Technical Support]

Hi Tim,

I think I've found the reason. In the source there is 

if (REPLACE_MODE.equals(acItem.getMode())) {
removeReadPolicies(item, TYPE_CUSTOM);
removeReadPolicies(item, TYPE_INHERITED);
}

so READ is only removed for TYPE_CUSTOM or TYPE_INHERITED and not any of 
the other types or if the type hasn't been set at all (which is the case 
with our data). 

Do you consider this to be a bug? 

BR
Maruan

Maruan Sahyoun schrieb am Freitag, 15. Dezember 2023 um 09:26:59 UTC+1:

> Hi Tim,
>
> I'm attaching a screenshot of the items policy setting before and after 
> having run bulk access together with the json and log. As there is already 
> a cusom setting for read and write maybe that's where it's getting confused 
> as you can see from the after screenshot that instead of replacing it's 
> adding also the control json is specifying replace.
>
> BR
> Maruan
>
> Maruan Sahyoun schrieb am Freitag, 15. Dezember 2023 um 09:14:30 UTC+1:
>
>> Hi Tim,
>>
>> thank you for your response. I've tried on the demo site where it works. 
>> Will investigate further.
>>
>> BR
>> Maruan
>>
>> DSpace Technical Support schrieb am Donnerstag, 14. Dezember 2023 um 
>> 23:18:34 UTC+1:
>>
>>> Hi Maruan,
>>>
>>> Assuming you selected to change the "Item's Metadata" and selected the 
>>> "Replace access conditions" mode, then the Item should only have one policy 
>>> (which matches with the new access condition type).  It's not exactly clear 
>>> to me why this wouldn't be working based on the details you provided.
>>>
>>> If this isn't working, then we may need more details about the steps you 
>>> are taking, or you might want to submit a bug ticket to 
>>> https://github.com/DSpace/dspace-angular/issues (with the step by step 
>>> process you took). You also are welcome to test this process out on the 
>>> demo site (https://demo.dspace.org), which is running 7.6.1, to see if 
>>> you can reproduce the issue there.
>>>
>>> Tim
>>>
>>> On Wednesday, December 13, 2023 at 10:20:51 AM UTC-6 
>>> maruan@googlemail.com wrote:
>>>
 I've a question regarding bulk access management and maybe a 
 misconception from my side.

 Currentl I have an item with READ permission for Anonymous. Now using 
 Bulk access management I'd like to change that to Administrator using 
 "Replace Access Conditions" and selecting "administrator" from the drop 
 down.

 After that I have READ permission for Administrator but still READ 
 permission for Anonymous.

 I'm using DSpace 7.6.0 - am I doing something wrong?

 BR
 Maruan 

>>>

-- 
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/dd3b7fe5-0d50-4f8f-9bac-5e8799a32f75n%40googlegroups.com.

[dspace-tech] Re: Bulk access management doesn't remove access conditions

['Maruan Sahyoun' via DSpace Technical Support]

Hi Tim,

thank you for your response. I've tried on the demo site where it works. 
Will investigate further.

BR
Maruan

DSpace Technical Support schrieb am Donnerstag, 14. Dezember 2023 um 
23:18:34 UTC+1:

> Hi Maruan,
>
> Assuming you selected to change the "Item's Metadata" and selected the 
> "Replace access conditions" mode, then the Item should only have one policy 
> (which matches with the new access condition type).  It's not exactly clear 
> to me why this wouldn't be working based on the details you provided.
>
> If this isn't working, then we may need more details about the steps you 
> are taking, or you might want to submit a bug ticket to 
> https://github.com/DSpace/dspace-angular/issues (with the step by step 
> process you took). You also are welcome to test this process out on the 
> demo site (https://demo.dspace.org), which is running 7.6.1, to see if 
> you can reproduce the issue there.
>
> Tim
>
> On Wednesday, December 13, 2023 at 10:20:51 AM UTC-6 
> maruan@googlemail.com wrote:
>
>> I've a question regarding bulk access management and maybe a 
>> misconception from my side.
>>
>> Currentl I have an item with READ permission for Anonymous. Now using 
>> Bulk access management I'd like to change that to Administrator using 
>> "Replace Access Conditions" and selecting "administrator" from the drop 
>> down.
>>
>> After that I have READ permission for Administrator but still READ 
>> permission for Anonymous.
>>
>> I'm using DSpace 7.6.0 - am I doing something wrong?
>>
>> BR
>> Maruan 
>>
>

-- 
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/3f05c82b-6af4-499d-9c35-823ca764b4a3n%40googlegroups.com.

[dspace-tech] Re: Bulk access management doesn't remove access conditions

['Maruan Sahyoun' via DSpace Technical Support]

Yes - that's of course something I've checked. It reports that it sets the 
items access

Andrew K schrieb am Mittwoch, 13. Dezember 2023 um 20:01:04 UTC+1:

> Has the bulk-access-control process finished successfully? (in the 
> Processes tab)
>
> середу, 13 грудня 2023 р. о 18:20:51 UTC+2 Maruan Sahyoun пише:
>
>> I've a question regarding bulk access management and maybe a 
>> misconception from my side.
>>
>> Currentl I have an item with READ permission for Anonymous. Now using 
>> Bulk access management I'd like to change that to Administrator using 
>> "Replace Access Conditions" and selecting "administrator" from the drop 
>> down.
>>
>> After that I have READ permission for Administrator but still READ 
>> permission for Anonymous.
>>
>> I'm using DSpace 7.6.0 - am I doing something wrong?
>>
>> BR
>> Maruan 
>>
>

-- 
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/06385a35-ebb0-4306-ba1d-ccf04dacfc2fn%40googlegroups.com.

[dspace-tech] Bulk access management doesn't remove access conditions

['Maruan Sahyoun' via DSpace Technical Support]

I've a question regarding bulk access management and maybe a misconception 
from my side.

Currentl I have an item with READ permission for Anonymous. Now using Bulk 
access management I'd like to change that to Administrator using "Replace 
Access Conditions" and selecting "administrator" from the drop down.

After that I have READ permission for Administrator but still READ 
permission for Anonymous.

I'm using DSpace 7.6.0 - am I doing something wrong?

BR
Maruan 

-- 
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/420708ae-8c95-4365-bce1-7a0b02954262n%40googlegroups.com.

[dspace-tech] Re: Batch import SAF zip but remap metadata fields

['Maruan Sahyoun' via DSpace Technical Support]

AFAIK there are serveral ways of doing this:
- go through the exported data and rename the fields. But that needs some 
programming
- if you have the old schema and new schema avail what you could do is to 
a) import first 
b) export the metadata only 
c) rename the columns accordingly
d) reimport the metadata
- do it on DB level using some SQL

I'd think if you don't like to go for programming/scripting or SQL the 
second option is the easiest as it's using built in capabilities.

BR
Maruan 

Ross schrieb am Donnerstag, 23. November 2023 um 10:02:45 UTC+1:

> Hi, 
>
> I want to do a batch import of SAF data that was exported from a previous 
> collection. In my new collection I have moved some metadata fields to other 
> schemas and changed some of the metadata field names.
>
> I am wondering how I can import the SAF data but map the existing metadata 
> to my updated metadata fields ?
>
> Example:
> OLD -> NEW
> dc.field -> mySchema.field
> dc.field2 -> mySchema.field3
>
> Thanks
>

-- 
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/ae46cfce-dadb-4af3-86fc-62019da16afbn%40googlegroups.com.

[dspace-tech] Re: Out Of Memory Error while trying to use filter-media command

['Maruan Sahyoun' via DSpace Technical Support]

You can raise the memory by either setting the JAVA_OPTS variable or 
setting the memory in the dspace.sh script

export JAVA_OPTS="-Xmx1024m -Dfile.encoding=UTF-8"
dspace filter-media

BR
Maruan

Salony Permanand schrieb am Dienstag, 21. November 2023 um 10:41:03 UTC+1:

> Hello Everyone,
>
> I am using Dspace version 7.6
>
> I created collections and imported items using zip. 
>
> In each item , I have 3 pdfs attached having size 100-200 MB
>
> I am trying to add thumbnail and full text indexing using filter-media 
> command
>
> But I am getting "OutOfMemoryError !!!Exception in thread "main" 
> java.lang.OutOfMemoryError: Java heap space in dspace filter-media"
>
> Attaching below scrnshot of error
>
> Please if anyone knows any solution, then explain
>

-- 
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/48e495ab-2831-4fd2-8ef8-f22fae5ee1ebn%40googlegroups.com.

[dspace-tech] Re: Error when creating collection

['Maruan Sahyoun' via DSpace Technical Support]

Never worked with DSpace-CRIS but you schould be able to download the 
missing definitions from the GitHub Repo

https://github.com/4Science/DSpace/tree/dspace-cris-2023.01.01/dspace/config/registries

I think cris-types is the one missing to overcome that message but you 
might also need the others.

BR
Maruan

Nicolas becerra morales schrieb am Montag, 20. November 2023 um 21:35:48 
UTC+1:

> Hello, I found the error too,  Will you have CRIS-related metadata schema 
> and instructions to perform this configuration? I would appreciate your help
> El lunes, 20 de noviembre de 2023 a las 16:45:15 UTC-3, Maruan Sahyoun 
> escribió:
>
>> the reason for the error is 
>> ...
>> Caused by: java.sql.SQLException: bad_dublin_core 
>> schema=cris.submission.definition. Metadata field does not exist!
>> ...
>>
>> It looks like you are running DSpace-CRIS but don't have the CRIS-related 
>> metadata schema installed.
>>
>> Nicolas becerra morales schrieb am Montag, 20. November 2023 um 16:40:32 
>> UTC+1:
>>
>>> El lunes, 20 de noviembre de 2023 a las 9:56:08 UTC-3, Nicolas becerra 
>>> morales escribió:
>>>
 Hello, thank you for wanting to help me, I will attach the dspace.log 
 to see if you can help me find the error, I appreciate your help in advance


 El lunes, 20 de noviembre de 2023 a las 9:45:28 UTC-3, Maruan Sahyoun 
 escribió:

> you wouldn't by any chance be able to get a hold of the server log 
> when this happens? Really difficult to tell from the frontend message 
> only.
>
> BR
> Maruan
>
> Nicolas becerra morales schrieb am Freitag, 17. November 2023 um 
> 16:00:56 UTC+1:
>
>> When trying to create a collection for a community I get an error, 
>> I'll attach image, I'm working locally
>> backend: 7.5
>> Frontend: DSpace CRIS 7 (based on 7.5 dspace frontend)
>>
>>

-- 
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/75cdde93-4e30-460b-8b9c-fa0fa39b2d25n%40googlegroups.com.

[dspace-tech] Re: Error when creating collection

['Maruan Sahyoun' via DSpace Technical Support]

the reason for the error is 
...
Caused by: java.sql.SQLException: bad_dublin_core 
schema=cris.submission.definition. Metadata field does not exist!
...

It looks like you are running DSpace-CRIS but don't have the CRIS-related 
metadata schema installed.

Nicolas becerra morales schrieb am Montag, 20. November 2023 um 16:40:32 
UTC+1:

> El lunes, 20 de noviembre de 2023 a las 9:56:08 UTC-3, Nicolas becerra 
> morales escribió:
>
>> Hello, thank you for wanting to help me, I will attach the dspace.log to 
>> see if you can help me find the error, I appreciate your help in advance
>>
>>
>> El lunes, 20 de noviembre de 2023 a las 9:45:28 UTC-3, Maruan Sahyoun 
>> escribió:
>>
>>> you wouldn't by any chance be able to get a hold of the server log when 
>>> this happens? Really difficult to tell from the frontend message only.
>>>
>>> BR
>>> Maruan
>>>
>>> Nicolas becerra morales schrieb am Freitag, 17. November 2023 um 
>>> 16:00:56 UTC+1:
>>>
 When trying to create a collection for a community I get an error, I'll 
 attach image, I'm working locally
 backend: 7.5
 Frontend: DSpace CRIS 7 (based on 7.5 dspace frontend)



-- 
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/10b811c9-70a9-4e68-9323-e66d0c1a1554n%40googlegroups.com.

[dspace-tech] Re: Error when creating collection

['Maruan Sahyoun' via DSpace Technical Support]

you wouldn't by any chance be able to get a hold of the server log when 
this happens? Really difficult to tell from the frontend message only.

BR
Maruan

Nicolas becerra morales schrieb am Freitag, 17. November 2023 um 16:00:56 
UTC+1:

> When trying to create a collection for a community I get an error, I'll 
> attach image, I'm working locally
> backend: 7.5
> Frontend: DSpace CRIS 7 (based on 7.5 dspace frontend)
>
>

-- 
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/44ed6720-c930-430a-946a-bb6f4d36811en%40googlegroups.com.

[dspace-tech] Re: Import of zip file not working on DSpace 7.6

['Maruan Sahyoun' via DSpace Technical Support]

if I'm not mistaken from the screenshots provided you were using the 
validate option.

According to the docs this doesn't actually import the data:

-v --validate 
test run - do not actually import items

BR
Maruan

Lewatle Johannes Phaladi schrieb am Freitag, 17. November 2023 um 09:23:55 
UTC+1:

> Hi Maruan,
>
> I have used frontend way to export and import collection, please see 
> attached document with steps I followed and all steps succeeded but there 
> is no items imported even if we did get success message that the items are 
> imported.
>
> Regards,
> Lewatle 
>
> On Wednesday, 15 November 2023 at 14:30:18 UTC+2 Maruan Sahyoun wrote:
>
>> Hi,
>>
>> what was been the export and import command you used? When importing did 
>> you choose a parent community? E.g. when using AIP
>>
>>
>> https://wiki.lyrasis.org/display/DSDOC7x/AIP+Backup+and+Restore#AIPBackupandRestore-RestoringEntireSite
>>
>> "... N*otice that unlike* *-s* *option (for submission/ingesting), the* 
>> *-r* *option does not require the Parent Object (**-p* *option) to be 
>> specified if it can be determined from the package itself. ..."*
>>
>> But as the note says  *IF* it can be determined: I had to specify the 
>> parent in the past most of the times. What I did when doing it via AIP was 
>> to
>>
>> BR
>> Maruan
>>
>> Lewatle Johannes Phaladi schrieb am Mittwoch, 15. November 2023 um 
>> 12:46:02 UTC+1:
>>
>>> Hi All,
>>>
>>> I have tried to use export and import features from DSpace 7.6 the aim 
>>> was to move collection with 600 items to new location on the same DSpace 
>>> installation, export of collection was done successfully, and import also 
>>> shows success message but when I go to collection after running import 
>>> there is no items imported despite success message.
>>>
>>> Please help.
>>>
>>> Regards,
>>> Lewatle  
>>>
>>

-- 
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/4c02f839-0e94-4de6-a2aa-44f3b6a139a9n%40googlegroups.com.

[dspace-tech] Re: Import of zip file not working on DSpace 7.6

['Maruan Sahyoun' via DSpace Technical Support]

Hi,

what was been the export and import command you used? When importing did 
you choose a parent community? E.g. when using AIP

https://wiki.lyrasis.org/display/DSDOC7x/AIP+Backup+and+Restore#AIPBackupandRestore-RestoringEntireSite

"... N*otice that unlike* *-s* *option (for submission/ingesting), the* *-r* 
*option 
does not require the Parent Object (**-p* *option) to be specified if it 
can be determined from the package itself. ..."*

But as the note says  *IF* it can be determined: I had to specify the 
parent in the past most of the times. What I did when doing it via AIP was 
to

BR
Maruan

Lewatle Johannes Phaladi schrieb am Mittwoch, 15. November 2023 um 12:46:02 
UTC+1:

> Hi All,
>
> I have tried to use export and import features from DSpace 7.6 the aim was 
> to move collection with 600 items to new location on the same DSpace 
> installation, export of collection was done successfully, and import also 
> shows success message but when I go to collection after running import 
> there is no items imported despite success message.
>
> Please help.
>
> Regards,
> Lewatle  
>

-- 
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/544a5b33-cd91-4bc0-9859-0c5c0a1f406cn%40googlegroups.com.

[dspace-tech] Re: Dspace 6.4 jspui interface not showing

['Maruan Sahyoun' via DSpace Technical Support]

did you follow the instruction in 
   
https://wiki.lyrasis.org/display/DSDOC6x/Installing+DSpace#InstallingDSpace-Installation
especially the section about choosing which UI you'd like to use (xmlui or 
jspui) and it's deployment (10. *Deploy Web Applications:)*
If the xmlui is available and working fine the base installation was 
successful but you have deployed the xmlui where you wanted the jspui.

BR
Maruan

Md Monirul Islam Ansari schrieb am Mittwoch, 8. November 2023 um 13:43:02 
UTC+1:

> Hello dear communities,
> in our library we tried to 
> install the dspace 6.4 version. after successfully run all the initial step 
> we able to view the *xmlui *interface. We are not so techno efficient so 
> don't know much about the backend stuff, as of now can anyone have a way 
> out, please provide us, we might be helpful to you.
>
> Also, we are using Linux Ubuntu as OS with 16GB RAM.
>
> Thanks and Regards,
>
>
> *Md Monirul Islam Ansari,Trainee, Central Library,NIT Agartala, Agartala, 
> Tripura*
>

-- 
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/f64f3c86-c885-4414-9ab8-b18568b3f7d4n%40googlegroups.com.

[dspace-tech] Re: Error

['Maruan Sahyoun' via DSpace Technical Support]

Just recently I did a fresh install with 7.6 and havn't experienced such 
issue. I even didn't have to change the memory settings. With that could 
you provide some additional information
- what's the yarn command you executed
- which node version are you on
- which yarn version are you on
- which DSpce version are you using
- which OS are you using

BR
Maruan

Nicolas becerra morales schrieb am Mittwoch, 8. November 2023 um 15:07:49 
UTC+1:

> Hello, does anyone know how to solve this error? According to the message, 
> I am out of memory to compile, but I have already tried placing 4, 8 and 9 
> of RAM but it still gives that error, has anyone solved it? I'd appreciate 
> your help
>

-- 
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/9768a742-56b4-498a-95ed-2597713a22c8n%40googlegroups.com.

[dspace-tech] Re: How to debug frontend

['Maruan Sahyoun' via DSpace Technical Support]

How did you start the frontend? In package.json you can see different 
options to run the frontend. I believe what you are looking for is to start 
it with

yarn start:dev

BR
Maruan
geethanjali alaguraj schrieb am Dienstag, 7. November 2023 um 06:05:45 
UTC+1:

> Hello,
>
> How to debug the front end can anyone tell the procedures . I have tried 
> angular devtools to debug the frontend code but it shows like this:
>
> We detected an application built with production configuration. Angular 
> DevTools only supports development builds. 
> How to resolve this or is there any other method to debug?.
>

-- 
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/a8c08b70-7b32-477b-8aa7-ab1c0f0fd8e8n%40googlegroups.com.

[dspace-tech] AIP Avoid creating license bundle

['Maruan Sahyoun' via DSpace Technical Support]

Hello,
I'm exporting content from DSpace 6 to be imported into DSpace 7 using AIP 
Backup and Restore. The DSpace 6 item does not have a license bundle but 
after import into DSpace 7 using Restore mode a license bundle is being 
created.

For aip.disseminate.rightsMD only METSRights is specified in DSpace 6.

For DSpace 7 
mets.dspaceAIP.ingest.crosswalk.DSpaceDepositLicense = NULLSTREAM
mets.dspaceAIP.ingest.crosswalk.CreativeCommonsRDF = NULLSTREAM
mets.dspaceAIP.ingest.crosswalk.CreativeCommonsText = NULLSTREAM

are defined.

What am I doing wrong? How can I avoid a license bundle being created.

BR and thank you in advance for your help on this topic
Maruan

-- 
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/42350295-1724-4447-8c9d-616529d4a667n%40googlegroups.com.

[dspace-tech] Re: Installation issue with DSpace 7.6

['Maruan Sahyoun' via DSpace Technical Support]

The issue has been resolved and was caused by an improper database 
installation. After fixing that the error is gone

Maruan Sahyoun schrieb am Montag, 30. Oktober 2023 um 18:12:44 UTC+1:

> Dear DSpace Community,
>
> upon a fresh install of DSpace 7 on a Linux Server using a Postgres DB I'm 
> getting below stack trace when running ant fresh_install.
>
> Would you have any pointers what might be causing this issue and how to 
> overcome that?
>
> With kind regards
> Maruan
>
> 
>
> test_database:
>  [java] Caught exception:
>  [java] org.postgresql.util.PSQLException: ERROR: relation 
> "schema_version" does not exist
>  [java]   Position: 23
>  [java] at 
> org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2713)
>  [java] at 
> org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2401)
>  [java] at 
> org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:368)
>  [java] at 
> org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:498)
>  [java] at 
> org.postgresql.jdbc.PgStatement.execute(PgStatement.java:415)
>  [java] at 
> org.postgresql.jdbc.PgPreparedStatement.executeWithFlags(PgPreparedStatement.java:190)
>  [java] at 
> org.postgresql.jdbc.PgPreparedStatement.executeQuery(PgPreparedStatement.java:134)
>  [java] at 
> org.apache.commons.dbcp2.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:122)
>  [java] at 
> org.apache.commons.dbcp2.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:122)
>  [java] at 
> org.dspace.storage.rdbms.DatabaseUtils.getCurrentFlywayState(DatabaseUtils.java:1556)
>  [java] at 
> org.dspace.storage.rdbms.FlywayUpgradeUtils.upgradeFlywayTable(FlywayUpgradeUtils.java:83)
>  [java] at 
> org.dspace.storage.rdbms.DatabaseUtils.main(DatabaseUtils.java:113)
>  [java] at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native 
> Method)
>  [java] at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>  [java] at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>  [java] at java.base/java.lang.reflect.Method.invoke(Method.java:566)
>  [java] at 
> org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:277)
>  [java] at 
> org.dspace.app.launcher.ScriptLauncher.handleScript(ScriptLauncher.java:133)
>  [java] at 
> org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:98)
>

-- 
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/77675f67-8bf8-4963-b06d-ebf0170a6080n%40googlegroups.com.

[dspace-tech] Installation issue with DSpace 7.6

['Maruan Sahyoun' via DSpace Technical Support]

Dear DSpace Community,

upon a fresh install of DSpace 7 on a Linux Server using a Postgres DB I'm 
getting below stack trace when running ant fresh_install.

Would you have any pointers what might be causing this issue and how to 
overcome that?

With kind regards
Maruan



test_database:
 [java] Caught exception:
 [java] org.postgresql.util.PSQLException: ERROR: relation 
"schema_version" does not exist
 [java]   Position: 23
 [java] at 
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2713)
 [java] at 
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2401)
 [java] at 
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:368)
 [java] at 
org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:498)
 [java] at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:415)
 [java] at 
org.postgresql.jdbc.PgPreparedStatement.executeWithFlags(PgPreparedStatement.java:190)
 [java] at 
org.postgresql.jdbc.PgPreparedStatement.executeQuery(PgPreparedStatement.java:134)
 [java] at 
org.apache.commons.dbcp2.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:122)
 [java] at 
org.apache.commons.dbcp2.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:122)
 [java] at 
org.dspace.storage.rdbms.DatabaseUtils.getCurrentFlywayState(DatabaseUtils.java:1556)
 [java] at 
org.dspace.storage.rdbms.FlywayUpgradeUtils.upgradeFlywayTable(FlywayUpgradeUtils.java:83)
 [java] at 
org.dspace.storage.rdbms.DatabaseUtils.main(DatabaseUtils.java:113)
 [java] at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native 
Method)
 [java] at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
 [java] at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 [java] at java.base/java.lang.reflect.Method.invoke(Method.java:566)
 [java] at 
org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:277)
 [java] at 
org.dspace.app.launcher.ScriptLauncher.handleScript(ScriptLauncher.java:133)
 [java] at 
org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:98)

-- 
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/ae951ea0-f240-4701-833e-8cc012775fffn%40googlegroups.com.