r each word/token/term in the
search (either in the frontend or config for Solr).
Changing the search algorithm from Lucine to Extended DisMax (eDisMax) Query
Parser. I’ve attempted this but no luck yet.
Does anyone have any practical advice/suggestions on how to improve this?
Kind Regards,
-
I could not find any problems with your configs.
понеділок, 21 жовтня 2024 р. о 16:38:47 UTC+3 Roberto Greiner пише:
# I place all the SSL entries in the following Include file to unclutter my
site definition file
But why not try the single site config file like in the manual? Something
might
. о 19:28:30 UTC+3 Israel Irizarry пише:
> Hey Andrew!
>
> That article is really helpful! I have already enabled it now, so my
> current issue is how to make the site available to the public once we get
> it all set up and ready.
>
> Thanks!
>
>
> *Israel Irizar
Hey Israel
You can use this
manual https://repozitar.fhv.uniza.sk/items/5b8d7e58-8e9c-4280-85d3-9d7c4b49b4d7
пʼятниця, 11 жовтня 2024 р. о 17:53:47 UTC+3 Israel Irizarry пише:
> Update again!
>
> I was able to fix the issue by just starting the frontend again. I did pm2
> start dspace-angular.j
WritePaths=/mnt/dspacedir
>
> The /mnt/dspacedir has been mounted. I can read (access) files attached to
> existing items but as stated earlier, i can't upload new files.
> Thanks for the help.
>
>
>
>
> On Thu, Jul 11, 2024 at 6:13 PM Andrew K wrote:
>
>>
Hi Mark,
Thanks a lot for the information!
I completely forgot that I did that.
What is the other way to adjust tomcat9 ReadWritePaths?
And, may I ask why updates like this go silently?
WBR,
Andrew
четвер, 11 липня 2024 р. о 17:57:58 UTC+3 Walk, Martin пише:
> Hi Andrew,
>
> thi
-1ubuntu0.4) ...Setting up tomcat9
(9.0.31-1ubuntu0.5) ...Processing triggers for rsyslog
(8.2001.0-1ubuntu1.3) ...Log ended: 2024-07-10 06:31:59*
Could those tomcat updates (no one started them, must be automatic) cause
the upload problem?
Where else should I look?
Thanks,
Andrew
--
All
Hi,
There's this tab "Access Control".
I use "local" group for local IPs, then I set permissiont for this group to
access bitstreams (files) or metadata (items).
WBR,
Andrew
[image: 2024-05-15_175719.png]
середу, 15 травня 2024 р. о 17:44:53 UTC+3 Young, Philip пише:
Yes, pretty aggressively, Stats for today:
*78575 Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible;
ClaudeBot/1.0; +claude...@anthropic.com)*
Googlebot is the next in the top crawlers with decent 5500 requests.
But I've seen worse load.
пʼятницю, 26 квітня 2024 р. о 18:51:54 UTC+3 Ja
ed pseudo-class
:lang*
What is the problem? How to solve it?
WBR,
Andrew
--
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
"DS
null WHERE requestitem_id =
2;UPDATE 1dspace=# UPDATE requestitem SET bitstream_id = null WHERE
requestitem_id = 3;UPDATE 1*
Problem solved! Thanks a lot!
Cleanup successfully finished now.
WBR,
Andrew
четвер, 21 березня 2024 р. о 22:43:11 UTC+2 Amy Ball Wicklund пише:
> You could try substituting r
b50) is still
referenced from table "requestitem".*
неділю, 17 березня 2024 р. о 16:07:38 UTC+2 Andrew K пише:
Hi!
I have the same error on cleanup. Trying to use this method to fix it.
But I receive 2 empty rows here instead of some uuids
*\set a 15b3ebc4-ae05-461e-ab9d-3a39bdb
gh
*dspace=# SELECT deleted FROM bitstream WHERE uuid = :'a';*
deleted
-
t
(1 row)
What do I do next?
Thanks,
Andrew
середу, 5 липня 2023 р. о 09:29:31 UTC+3 Technologiczny Informator пише:
> Hi,
>
> Mark was replying to my post then. While cleaning I had the same on
root@dspace:/dspace/DSpace-dspace-7.6.1/dspace/target/dspace-installer# ant
fresh_install
Buildfile:
/dspace/DSpace-dspace-7.6.1/dspace/target/dspace-installer/build.xml
init_installation:
prepare_configs:
[mkdir] Created dir:
/dspace/DSpace-dspace-7.6.1/dspace/target/dspace-installer/conf
Hi Tim,
Unfortunately not all links are redirected automatically.
Links with spaces or cyrillic symbols in the filename fail to open.
Best regards,
Andrew
середу, 6 березня 2024 р. о 17:44:00 UTC+2 DSpace Technical Support пише:
> Hi Sean,
>
> Correct, DSpace 7 will only display/show
UPD: ORCID authentification still fails in some browsers like older Chrome
109 (Win7).
пʼятницю, 1 березня 2024 р. о 00:34:51 UTC+2 Andrew K пише:
UPD: It's the same issue https://github.com/DSpace/DSpace/issues/9109
Moving
*plugin.sequence.org.dspace.authenticate.AuthenticationM
ethod =
org.dspace.authenticate.OrcidAuthentication*
fixed the ORCID authentification.
Also, ORCID login button moved down where it was before. Great
пʼятницю, 1 березня 2024 р. о 00:21:19 UTC+2 Andrew K пише:
> Hello!
>
> I moved from 7.6 server to a 7.6.1 server.
> Looks like every possible setting is made.
> But OR
admin credentials, press Login and... I'm logged with the ORCID profile,
not admin!
Thanks,
Andrew
--
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 subscrib
It shows eactly 2 items now...
середу, 28 лютого 2024 р. о 15:05:45 UTC+2 Caty пише:
This collection has 2 items (one existent and one added by me), but it
shows collection item counter 1: "Coleção de teste (1)"
--
All messages to this mailing list should adhere to the Code of Conduct:
htt
Hi Caty,
It depends on how you define "working well". I just don't expect immediate
updates. Not sure how long it takes, but AFAIK the next day the numbers
look good. That's well enough for me )
WBR,
Andrew
понеділок, 26 лютого 2024 р. о 15:06:06 UTC+2 Caty пише:
> H
oogle.com/u/2/g/dspace-tech/c/GshVU2RXE8w/m/FTUL2eCWBQAJ
But in my case it says nothing about very long strings, just error
Any help would be appreciated.
Thank you!
WBR,
Andrew
--
All messages to this mailing list should adhere to the Code of Conduct:
https://www.lyrasis.org/about/Pages/Code-
I forgot to mention that nothing pops out in the logs.
--
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" gr
left logo and open a few instances in new tabs
- some of them load OK, some of them have 500 error.
The server load is very low, like 0.5.
I looked to the browser console. There are some errors, attached.
Please help eliminate this problem!
Thanks,
Andrew
[image: 2024-02-10_163348.png][image:
Hi!
Is it possible to give access to items based on user-agent?
Thanks,
Andrew
--
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
Hello!
Is it possible to run filter-media for each new item automatically?
Best regards,
Andrew
--
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
Hello Sidney,
A local DNS server can easily solve the problem.
середу, 20 грудня 2023 р. о 13:32:18 UTC+2 Sidney Campos пише:
> *Good morning!*
>
> *I continue on my mission to make DSpace work perfectly on my Windows 10
> server*
>
> With the current settings, I can access DSpace on the serve
Hi Steve,
Here's the manual I followed to switch to SSL
https://repozitar.fhv.uniza.sk/items/5b8d7e58-8e9c-4280-85d3-9d7c4b49b4d7
I also noticed that you have nameSpace: /xmlui in the config files. I think
it should be nameSpace: /
Best regards,
Andrew
понеділок, 18 грудня 2023 р. о 23:
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 Ano
Hey Sean!
That worked! You're a lifesaver! Thanks a lot!
WBR,
Andrew
вівторок, 5 грудня 2023 р. о 23:47:14 UTC+2 Sean Kalynuk пише:
> Hi Andrew,
>
>
>
> The public API URL is:
>
>
>
> https://pub.orcid.org/v3.0
>
>
>
> The http
OK, I'm out of options already
I enabled ORCID auth plugin. Set everything correctly in orcid.cfg
initialize-entities - done
create a Collection for "Person" entities - done
config/modules/researcher-profile.cfg - done
config/modules/authority.cfg - done
I am able to create my Researcher Profile.
dspace log has nothing about it
tomcat log has this for every authentification attempt
127.0.0.1 - - [03/Dec/2023:10:05:29 +0200] "GET
/server/api/authn/orcid?code=KNOI5s HTTP/1.1" 302 -
субота, 2 грудня 2023 р. о 20:49:40 UTC+2 Andrew K пише:
> Probably worth metnioning that the
Probably worth metnioning that the return URL in browser is
https://my.dspace.website/error?status=401&code=orcid.generic-error
I.e., that might be another error not related to the account email address.
And I use public API key.
субота, 2 грудня 2023 р. о 20:20:00 UTC+2 Andrew K пише:
&
usted parties might have *Access type: Read your
information with visibility set to Trusted Parties*.
I.e. that looks like DSpace doesn't even ask for the email, right?
WBR,
Andrew
--
All messages to this mailing list should adhere to the Code of Conduct:
https://www.lyrasis.org/about/Pag
it doesn't scale linear, 8 cores should overperform 4 cores,
right?
Best regards,
Andrew
четвер, 16 листопада 2023 р. о 19:07:18 UTC+2 Plate, Michael пише:
> Hi Andrew,
>
> be careful on the number of CPUs (Cores) you assign to the VM - this may
> be a boomerang if the host can
pretty much enough for a modest repository like
ours (13K items).
Thus 8-10 CPU cores should do the job. As for RAM amount, it's never too
much, but 10-12GB should be OK (on our VDS hosting RAM is a lot more
expensive, 1GB RAM equals 10 CPU cores).
Best regards,
Andrew
понеділок, 20 листопада 2
st regards,
Andrew
четвер, 16 листопада 2023 р. о 00:56:22 UTC+2 DSpace Technical Support пише:
> Hi Andrew,
>
> We're aware that these i18n files can get "out of sync" easily and are
> working on ways to improve that. See this ticket:
> https://github.com/DSpace/d
Hi Hrafn!
Thanks! I am also somewhat hopeful about the new release. In my situation
first thing I looked for were fixed performance issues )
Best regards,
Andrew
четвер, 16 листопада 2023 р. о 15:32:46 UTC+2 Hrafn Malmquist пише:
> Hi guys
>
> I would consider upgrading to 7.6.1. Th
s not the best
in my case).
But at least the server is not chocking with multiple requests. That is a
very big deal! Amazing. Thank you!
The speed index is 1-2s now instead of 5s! That is acceptable.
Best regards,
Andrew
четвер, 16 листопада 2023 р. о 15:47:21 UTC+2 dataquest пише:
> Hi,
be cached 100%.
But it always loads as if there's no cache... It actually looks like it
loads as long as for a logged user.
I have
anonymousCache:
max: 50
timeToLive: 720 # 3 hours
allowStale: true
That should work, right?
Best regards,
Andrew
--
All messages to thi
Hello Alex
You need to enable webui.strengths.show in dspace.cfg
It is available in DSpace 7.6.
WBR,
Andrew
вівторок, 14 листопада 2023 р. о 10:08:32 UTC+2 Alex B пише:
> Dear colleagues, please help me display the filter values on the home page.
>
> For example -
>
> [image:
n and plan to do is increase the number of cores to 12. That
should speed it up a little more.
Then I suppose we all should wait for DSpace to get more optimized )
Thanks again!
Best regards,
Andrew
вівторок, 14 листопада 2023 р. о 09:50:36 UTC+2 dataquest пише:
> Dear Andrew.
>
OK, I suddenly realized that DSpace log works only when I run scripts like
index-discovery, filter-media etc. Nothing on the web activity
So, the latest description of the problem:
Any page loads for a very long time, like 30s. But when it's loaded, the
navigation works pretty fast within the br
листопада 2023 р. о 20:38:51 UTC+2 Andrew K пише:
> Another very interesting observation.
> I load the main page. It takes a while. Then I click the links, everything
> works perfectly, list the items by date, list the communities... everything.
> So, I find some item and open it (works
Another very interesting observation.
I load the main page. It takes a while. Then I click the links, everything
works perfectly, list the items by date, list the communities... everything.
So, I find some item and open it (works pretty fast again, all in the same
tab). Then I copy the link and i
Hello Hrafn,
It was 5.4 (it actually still is, I only switched DNS to the new server).
But the old server had no https, unfortunately.
понеділок, 13 листопада 2023 р. о 16:48:51 UTC+2 Hrafn Malmquist пише:
> Hello Andrew
>
> Out of curiosity, what version was the old server that work
I forgot to mention the server capacity: 4 cores, 6GB RAM (12GB doesn't
change a lot), 200GB.
--
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 Goog
hly. The DSpace server is on the VDS and it works through
apache proxy (for https).
This is very disappointing. The old server worked lke a charm, always
instant response.
Please help me trace the source of errors.
WBR,
Andrew
PS: That said, once the page has loaded, clicking the links like sta
ld be much much better if the English names were shown
instead.
Is that possible?
Best regards,
Andrew
P.S.:
--
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 subscri
?
Thanks,
Andrew
понеділок, 16 жовтня 2023 р. о 23:13:11 UTC+3 DSpace Technical Support пише:
> Hi Andrew,
>
> Apologies for not getting back to this. I'm not always able to answer
> questions on this list quickly, but I see no one else has gotten to this
> one.
>
> The &
I probably should have mentioned that I run
*sudo /dspace/bin/dspace index-discovery -b*
on the new server first and it went OK.
After that I did
*sudo /dspace/bin/dspace filter-media*
and then
*sudo /dspace/bin/dspace index-discovery*
throws the error *java.lang.IllegalArgumentException: More t
quot; does not exist GRANT*
There was *psql* role and user instead of *postgres *on the old server.
Is that a problem I should correct somehow?
Thanks,
Andrew
середа, 4 жовтня 2023 р. о 23:08:42 UTC+3 DSpace Technical Support пише:
> Hi Andrew,
>
> As that "Caused by" error
The error message also has this string
Caused by: java.nio.file.NoSuchFileException:
/www/dspace/solr/statistics/data/index/segments_1
середа, 4 жовтня 2023 р. о 22:41:35 UTC+3 Andrew K пише:
Hello Tim,
Thank you! I don't know how but the database was not imported. The problem
s
DSpace Technical Support пише:
> Hi Andrew,
>
> Based on the information you shared, it appears (to me) that you ran the
> "dspace database migrate ignored" command on an **empty** database. If you
> look, the "info" command reported that the "Installe
pt has completed
sudo /dspace/bin/dspace filter-media
The script has started
The script has completed
But both scripts run very fast and the server shows no content (the
interface is available).
What can be wrong?
Thanks,
Andrew
--
All messages to this mailing list should adhere to the C
Hi there,
I followed the instruction here:
https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-FrontendRequirements
I used NGinx and on frontend installation:
- step 5; used YAML configuration
- step 6: run via PM2
Everything went well but after finishing up th
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
?
Thanks,
Andrew
--
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
Hey Lewatle,
1. Did you have this problem with Google Scholar indexing on a
previous DSpace versions?
2. What exactly have you done? *google-metadata.enable* = *true *is
default in DSpace 7.
Thanks
Andrew
четвер, 23 березня 2023 р. о 10:44:09 UTC+2 Lewatle Johannes Phaladi пише:
> D
Hi Tim,
Thank you!
DSpace has excellent support.
Best regards,
Andrew
вт, 21 бер. 2023 р. о 21:54 'Tim Donohue' via DSpace Technical Support <
dspace-tech@googlegroups.com> пише:
> Hi Andrew,
>
> DSpace 7 UI's URLs are not customizable. However, all old-style
sible for those old submissions.
So I just truncated the *workspaceitem* table in the database. And it
worked! Now index-discovery goes smoothly. Yay!
Can I also ask you if it's possible to keep the old handle-type URLs in
DSpace 7 ?
Best regards,
Andrew
вт, 21 бер. 2023 р. о 18:34
Hello!
I have a 7.5 server updated from 5.4.
The database update process finished OK.
But the index-discovery fails.
2023-03-20 09:24:03.611 INFO index-discovery - 4 @ The script has started
2023-03-20 09:24:03.611 INFO index-discovery - 4 @ Updating Index
2023-03-20 09:24:43.049 ERROR index-d
?
Thanks,
Andrew
--
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 grou
Of cause you must restart Tomcat after changes.
среда, 8 ноября 2017 г., 17:30:08 UTC+7 пользователь pontiu...@gmail.com
написал:
>
> Hello everyone,
>
>
>
> I have to configure the swordv2 server on an exisitng Dspace 5
> installation to allow access via swordV2 protocol. According to duraspac
On my installation the same pathes and changes have effect. I've added such
options to this file:
simpledc.uri = dc.identifier.uri
simpledc.issn = dc.identifier.issn
simpledc.x-doi = dc.identifier.x-doi
...
And it works ok. All necessary metadata fields are saved to items on DSpace.
с
I have such exception in DSpace log on pressing button "Import Now" for
collection:
java.text.ParseException: Unparseable date: "2017GMT-10-24"
at java.text.DateFormat.parse(DateFormat.java:357)
at org.dspace.core.Utils.parseISO8601Date(Utils.java:377)
at org.dspace.harvest.OAIHarvester.processRe
Thanks for letting me know, Hardy. With regard to Windows, I did follow the
Windows instructions when setting everything up and virtualization support
is definitely turned on.
Cheers,
Drew
On Wednesday, May 10, 2017 at 10:45:36 AM UTC-5, Hardy Pottinger wrote:
>
> Hi, Andrew, we have
I get the same error as you do (with the same output).
Running vagrant up --debug appears to show the connection is being refused
by puppetlabs.
DEBUG ssh: stderr: Unable to connect to https://forgeapi.puppetlabs.com:
Connection reset by peer
INFO interface: info: Unable to connect to
htt
Thanks for the response.
While I can add a policy to a bitstream in the Contents file, I
unfortunately can't seem to add a start date for that policy. As far as I
can tell (disclaimer: new to DSpace), what's included there isn't parsed
for a start date -- the import code just checks for the ac
Setting up embargoes in DSpace has been a little bit more confusing than I
expected.
What I would like to be able to do is: a) batch upload new items to DSpace
in Simple Archive Format with embargoes that are added for each item based
on included metadata, and b) batch edit already uploaded i
Running *mvn package -Dmirage2.on=true *as the dspace user, I get this
error:
[ERROR] Failed to execute goal on project xmlui-mirage2: Could not resolve
dependencies for project org.dspace.modules:xmlui-mirage2:war:7.0-SNAPSHOT:
Failed to collect dependencies at rubygems:compass:gem:1.0.1 -> ru
I ran vagrant up after deleting the box image and running vagrant destroy -f
, but I still got the previously referred to errors.
--
You received this message because you are subscribed to the Google Groups
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving ema
Hi Hardy,
I am also on 1.8.6, and I have installed vagrant-vbguest.
Thanks,
Drew
--
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+unsub
The failure messages and errors Andrea pointed out are all in my debug log
as well.
I'm new to Vagrant, so I'm afraid I don't have too many ideas for
troubleshooting!
--
You received this message because you are subscribed to the Google Groups
"DSpace Technical Support" group.
To unsubscri
Having a very similar issue. In the debug log, I can see the warden errors
at the end of your snippet. Vagrant up --debug ends with the "SSH
responded with a non-zero exit status" message.
I can SSH in, but the /home/vagrant/dspace-src folder is empty and
/home/vagrant/dspace just contains
this a known error? If so, is there a workaround?
Thanks,
Andrew
--
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-tec
after first time installing I get an Internal System Error when trying to
create a community for the first time. I am logged in as admin.
Source Code:
Internal System Error
The system has experienced an internal error. Please try to do what you
were doing again, and if the problem persists, p
76 matches
Mail list logo
