[dspace-tech] Re: What is VuFind and have you configured your DSpace 7.6 to import external metadata from it?

[Rupinder Singh]

HI, 
Vufind is a Discovery software that adds a discovery interface on top of 
your other library software like dspace, or Koha, OJS, or any knowledge 
management software that you use in your library. The benefit it provides 
is, VuFind can provide a single-window search retrieval system for all your 
different library software. VuFind can connect to this software using 
OAI-PMH protocol to fetch and harvest metadata records and then index it 
locally in its solr search engine. 
Once that is done, You and your library users will be able to search and 
retrieve content from all your connected silos(Koha, Dspace, OJS). , at a 
single web interface, without going to individual software. Your search 
will also work, even if any of the connected software goes offline, in that 
case, Vufind will retrieve results from its local index. 

It is an amazing Open Source software if you want to implement a discovery 
system on top of your discrete knowledge management software. 

Regards
Rupinder Singh

On Wednesday 29 May, 2024 at 2:36:38 am UTC+5:30 Carolyn Sullivan wrote:

> Hello all,
>
> I'm reviewing the options for importing external metadata to our DSpace 
> 7.6 instance to ensure we have all our API keys configured and etc.  One of 
> the options for importing external metadata is through a resource called 
> VuFind.  I googled it and found that it's apparently a discovery system.  
> Is this discovery system mostly available as an option for import to DSpace 
> for libraries running an instance of VuFind locally?  Would a local 
> researcher be likely to use VuFind if my institution wasn't running VuFind 
> anyways?  Trying to figure out (1) whether to configure it and (2) what id 
> I'd be using to pull in metadata if I DID configure it.
>
> Thanks,
> Carolyn.
>

-- 
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/80e43af4-c5e7-4bba-a4c0-12aaa44d2eaan%40googlegroups.com.

[dspace-tech] create-administrator problem

[Carlos Casado Vargas]

When trying to create an administrator account and it throws me the 
following error message:

First name: Admin
Last name: Istrator
Is the above data correct? (y or n): y
Password will not display on screen.
Password: 
Again to confirm: 
Exception: Error while configuring authority control, metadata field: 
dc.relation.funding could not be found
java.lang.IllegalStateException: Error while configuring authority control, 
metadata field: dc.relation.funding could not be found
at 
org.dspace.content.authority.MetadataAuthorityServiceImpl.init(MetadataAuthorityServiceImpl.java:154)
at 
org.dspace.content.authority.MetadataAuthorityServiceImpl.makeFieldKey(MetadataAuthorityServiceImpl.java:308)
at 
org.dspace.content.DSpaceObjectServiceImpl.addMetadata(DSpaceObjectServiceImpl.java:457)
at 
org.dspace.content.DSpaceObjectServiceImpl.addMetadata(DSpaceObjectServiceImpl.java:220)
at 
org.dspace.content.DSpaceObjectServiceImpl.addMetadata(DSpaceObjectServiceImpl.java:442)
at 
org.dspace.content.DSpaceObjectServiceImpl.setMetadataSingleValue(DSpaceObjectServiceImpl.java:559)
at org.dspace.eperson.EPerson.setLastName(EPerson.java:289)
at 
org.dspace.administer.CreateAdministrator.createAdministrator(CreateAdministrator.java:276)
at 
org.dspace.administer.CreateAdministrator.negotiateAdministratorDetails(CreateAdministrator.java:209)
at 
org.dspace.administer.CreateAdministrator.main(CreateAdministrator.java:107)
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:303)
at 
org.dspace.app.launcher.ScriptLauncher.handleScript(ScriptLauncher.java:153)
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/ea9d70e3-4a84-4c87-be1e-38871e79c856n%40googlegroups.com.

[dspace-tech] articles not listed google scholar search

[Samdani Shaik]

Hello Team,

we have created a new Dspace website, had 1000+ published articles. Its 
been 8 months.

I am unable to find these articles in google search, 
As I am new to these kind of repositories, can anyone suggest me what 
should be done to get indexed in google scholar. 

Thanks in advance and any support will appreciated.

Regards,
Samdani.

-- 
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/42a3d5d8-7f04-4890-ba83-e4cee14c0d82n%40googlegroups.com.

[dspace-tech] What is VuFind and have you configured your DSpace 7.6 to import external metadata from it?

[Carolyn Sullivan]

Hello all,

I'm reviewing the options for importing external metadata to our DSpace 7.6 
instance to ensure we have all our API keys configured and etc.  One of the 
options for importing external metadata is through a resource called 
VuFind.  I googled it and found that it's apparently a discovery system.  
Is this discovery system mostly available as an option for import to DSpace 
for libraries running an instance of VuFind locally?  Would a local 
researcher be likely to use VuFind if my institution wasn't running VuFind 
anyways?  Trying to figure out (1) whether to configure it and (2) what id 
I'd be using to pull in metadata if I DID configure it.

Thanks,
Carolyn.

-- 
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/9eb0aa55-5ab9-409e-9ad8-aebb4d13866en%40googlegroups.com.

[dspace-tech] Dspace on Ubuntu 24.04

[Rupinder Singh]

Hi,
I just updated my dspace server to latest 24.04. and it made the installed
tomcat 9 non functional.. when I checked the package was not there. When it
tried reinstalling it with apt, it says "this release candidate is not
available". So I installed whatever version was available on 24.04, which
was Apache 10.
Now my dspace server is not showing anything on 8080 REST interface, and
web interface on port 4000 shows an error 500.


What is the problem?

Thanks
Rupinder Singh

-- 
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/CAMLo0tUHEm6KCLc9iRKGsPO%2BakDz_Kvez0x-%3DweU6zwMinWT%3DQ%40mail.gmail.com.

[dspace-tech] Private message regarding: Private message regarding: Issue after restore all from DSpace 5 to Dspace 7

[dba...@gmail.com]

Thanks again, Tim.

I had previously tested with single Communities and Collections and they 
were working OK -- and that's why I proceeded with the whole-site AIP.

I'm going to look into the Migration technique you linked to. Hopefully 
I'll get that to work. Alternatively, I may end up just having to use AIPS 
one Collection or Community at a time.

Thanks for all the help.
David

On Wednesday, May 22, 2024 at 5:09:25 PM UTC-4 DSpace Technical Support 
wrote:

Hi David,

I'd recommend trying one of the following:

Potentially break down the task by trying to restore a *single* Community 
or Collection.  Once you get one restore to work, the others should all 
work similarly.  You could even try this on a test server to just ensure a 
basic restore works properly before running the larger restore. (If you 
wanted you also could do the entire restore in batches of this sort rather 
than all at once)

Alternatively, you could avoid AIPs altogether and use the Migration 
technique described here: 
https://wiki.lyrasis.org/display/DSDOC7x/Migrating+DSpace+to+a+new+server  
This migration can be used to upgrade from an older version of DSpace to a 
newer one, and there are a number of comments at the bottom of that page of 
other DSpace users who've said this works very well for larger sites.

AIPs are not the fastest way to move data around because they require a lot 
of time to unzip/process (and the current code is likely not the most 
efficient).  AIPs are excellent for restoring individual objects and can be 
very useful to restore from backup in an emergency scenario (or accidental 
deletion). They just are not as efficient as the migration process 
described above or the normal upgrade procedure 
.

Hopefully that gives you a few options to look at, but let us know if you 
have other questions.

Tim



On Wednesday, May 22, 2024 at 8:00:33 AM UTC-5 dba...@gmail.com wrote:

Thanks, Tim. 

I checked for content in community, collection, and item tables and they 
were all empty. I'm not sure what went wrong. The restore took about 2 
weeks for 200+ GB of data from a local disk. Is there any way to speed up 
the restore? It makes it really hard to troubleshoot when you have to wait 
so long for results.

Thanks,
David

On Tuesday, May 21, 2024 at 10:14:01 AM UTC-4 DSpace Technical Support 
wrote:

Hi,

Have you tried reindexing everything?  Assuming the import worked properly 
(no obvious errors in logs), then it's possible the content isn't showing 
because the reindex process either hasn't been triggered or somehow failed.

So, I'd recommend trying:  "[dspace]/bin/dspace index-discovery -b"   while 
Tomcat/Solr are running.  This may take a while for a large amount of 
content, but you should be able to watch its progress via the dspace.log.

If that doesn't work, then I'd recommend checking that your database *has 
content* in the "community", "collection" and "item" tables.  If there's 
nothing in there, then the problem was with the import process.The 
error you received from the "update-sequences" script almost sounds like it 
cannot see any content in the "handle" table, which again may imply the 
import didn't work as expected.

Tim

On Monday, May 20, 2024 at 8:44:09 AM UTC-5 dba...@gmail.com wrote:

I have a DSpace 5.10 instance that I have exported the entire site from 
using AIP.

I have a freshly installed DSpace 7.6.1 instance that I have imported all 
content into (
[dspace]/bin/dspace packager -r -a -f -t AIP -e  -i 
/0 -o skipIfParentMissing=true 
/full/path/to/your/site-aip.zip). 
The import was successful and imported over 200 GB of data.

However, when I log into the new instance, I do not see any communities or 
collections. I performed a server reboot to make sure all services were 
restarted OK, but still no communities/collections. I also tried to run 
'dspace database update-sequences', but I get the following error:

Running org/dspace/storage/rdbms/sqlmigration/postgres/update-sequences.sql
Caught exception:
org.postgresql.util.PSQLException: ERROR: setval: value 0 is out of bounds 
for sequence "handle_seq" (1..9223372036854775807)
at 
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2713)
at 
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2401)
at 
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:368)
at 
org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:498)
at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:415)
at 
org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:335)
at 
org.postgresql.jdbc.PgStatement.executeCachedSql(PgStatement.java:321)
at 
org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:297)
at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:292)
at 

Re: [dspace-tech] Export to CSV in Administrator Workflow

[Emilia Lobo]

Thanks for your answer. I am using version 7.6.1 of DSpace. The button is 
still not shown.

Emilia.-
El martes, 28 de mayo de 2024 a las 10:18:24 UTC-3, Morgan, Paige escribió:

>
> Hi, Emilia--
>
> Are you running 7.1? I remember when I encountered this problem myself – 
> it turned out that the export button had been written into the interface, 
> but it didn't actually have any functionality behind it. 
>
> I did, at Tim Donohue's suggestion, put in a ticket suggesting that 
> functionality be built in, but I don't think anything has happened with 
> that, and in more recent versions (7.4), the icon/button has been removed.
>
> Good luck!
> Paige
>
> -
> *Meeting/regular work hours: Monday - Friday, 9am-4:30pm*
>
> *Dr. Paige C. Morgan*
> (she/they)
>
> Digital Publishing and Copyright Librarian,
> Head of Digital Initiatives & Preservation
> University of Delaware Library, Museums and Press (on 
> Lenape land )
> Morris 118
> ORCID: https://orcid.org/-0001-8076-7356
> pai...@udel.edu
> 302.831.7153 <(302)%20831-7153>
>
> *** I observe email-free evenings and weekends. ***
>
>
> 
>  Book 
> time to meet with me 
> 
>  
> --
> *From:* dspac...@googlegroups.com  on behalf 
> of Emilia Lobo 
> *Sent:* Monday, May 27, 2024 09:54
> *To:* DSpace Technical Support 
>
> *Subject:* Re: [dspace-tech] Export to CSV in Administrator Workflow
> search-export-metadata
>
> Hello!, 
> This process indicates that it completed successfully but I don't see 
> where to download the completed script from the administrator account. 
> I don't see any link to recover that generated file. 
> What can be? 
> Thanks,
> Emilia
>
> El miércoles, 30 de noviembre de 2022 a las 18:11:20 UTC-3, Tim Donohue 
> escribió:
>
> Hi Paige,
>
> Yes that makes sense. It's clear that in your use case this "Export to 
> CSV" is not for "Batch Metadata Editing"... it's just to generate a basic 
> "status report" of items in workflow. 
>
> If you would, could you or Keith submit a bug ticket to 
> https://github.com/DSpace/dspace-angular/issues ?   I'd recommend adding 
> the step by step instructions for reproducing the error. Then add in some 
> basic details of how you'd like to use this feature.   I can then see if I 
> can find someone to work on this in the near future, with the hope that we 
> can fix it (instead of remove it).  They will have to investigate the 
> underlying issue though to see if it's easier to fix quickly.. or remove it 
> (to solve the bug) temporarily & fix later.   
>
> Overall though, the more I look at this feature, the more I think this was 
> accidental & never meant to appear on that page. :)  So, it may turn out to 
> be a happy accidental feature!
>
> Tim
>
> On Wednesday, November 30, 2022 at 2:57:55 PM UTC-6 pai...@udel.edu wrote:
>
> Hi Tim,
>
> Thanks for this response! For use cases, I would find it helpful to have 
> in process workflow items exportable as a way of tracking what’s going on 
> with items that are in process, and/or that have been orphaned. When we 
> were running DSpace 5.3, there was no way for an administrator to even see 
> broadly what was happening, and what workflow items *were* in process. We 
> have a number of items that have been hanging out in that space, and this 
> is the first time that I've actually been able to see them.
>
> My hope is that I can work on cleaning those up, and then not have so many 
> sitting around -- but I would find it very helpful to be able to check and 
> export a CSV periodically, just to check in with folks who use the workflow 
> setup.
>
> Does that make sense as a use case?
>
> Thanks again,
> Paige
>
> On Wed, Nov 30, 2022 at 15:36 Tim Donohue  wrote:
>
> Hi Paige & Keith,
>
> I can confirm this is happening locally for me as well.  It looks like a 
> possible bug.  This "Export to CSV" works fine in normal search results & 
> also in the "Your submissions" part of MyDSpace.  But, I can verify that it 
> doesn't work when viewing "Workflow tasks".
>
> That said, I admit, I wonder if that "Export to CSV" link should even 
> appear on the "Workflow tasks" page, as it's not really possible to perform 
> batch metadata editing on "Workflow tasks". (The Export to CSV feature is 
> primarily used for Batch Metadata Editing purposes)
>
> So, this is all to say, I think there's a bug here.  But, the bug might be 
> that the option even appears on this page.  Is this a specific use case you 
> had for wanting to export Workflow Tasks to CSV?  Just curious as maybe 
> there's a way to get this possibly accidental feature "working" rather than 
> remove it altogether.  Either way, I do think this is a bug, I'm just not 
> sure 

Re: [dspace-tech] Export to CSV in Administrator Workflow

[Morgan, Paige]

Hi, Emilia--

Are you running 7.1? I remember when I encountered this problem myself – it 
turned out that the export button had been written into the interface, but it 
didn't actually have any functionality behind it.

I did, at Tim Donohue's suggestion, put in a ticket suggesting that 
functionality be built in, but I don't think anything has happened with that, 
and in more recent versions (7.4), the icon/button has been removed.

Good luck!
Paige

-
Meeting/regular work hours: Monday - Friday, 9am-4:30pm


Dr. Paige C. Morgan

(she/they)
Digital Publishing and Copyright Librarian,
Head of Digital Initiatives & Preservation
University of Delaware Library, Museums and Press (on Lenape 
land)
Morris 118
ORCID: https://orcid.org/-0001-8076-7356
paig...@udel.edu
302.831.7153

** I observe email-free evenings and weekends. **

[cid:47c69843-1b18-4174-80a9-8193c3e74b03]
 Book time to meet with 
me

From: dspace-tech@googlegroups.com  on behalf of 
Emilia Lobo 
Sent: Monday, May 27, 2024 09:54
To: DSpace Technical Support 
Subject: Re: [dspace-tech] Export to CSV in Administrator Workflow

search-export-metadata

Hello!,
This process indicates that it completed successfully but I don't see where to 
download the completed script from the administrator account.
I don't see any link to recover that generated file.
What can be?
Thanks,
Emilia

El miércoles, 30 de noviembre de 2022 a las 18:11:20 UTC-3, Tim Donohue 
escribió:
Hi Paige,

Yes that makes sense. It's clear that in your use case this "Export to CSV" is 
not for "Batch Metadata Editing"... it's just to generate a basic "status 
report" of items in workflow.

If you would, could you or Keith submit a bug ticket to 
https://github.com/DSpace/dspace-angular/issues ?   I'd recommend adding the 
step by step instructions for reproducing the error. Then add in some basic 
details of how you'd like to use this feature.   I can then see if I can find 
someone to work on this in the near future, with the hope that we can fix it 
(instead of remove it).  They will have to investigate the underlying issue 
though to see if it's easier to fix quickly.. or remove it (to solve the bug) 
temporarily & fix later.

Overall though, the more I look at this feature, the more I think this was 
accidental & never meant to appear on that page. :)  So, it may turn out to be 
a happy accidental feature!

Tim

On Wednesday, November 30, 2022 at 2:57:55 PM UTC-6 pai...@udel.edu wrote:
Hi Tim,

Thanks for this response! For use cases, I would find it helpful to have in 
process workflow items exportable as a way of tracking what’s going on with 
items that are in process, and/or that have been orphaned. When we were running 
DSpace 5.3, there was no way for an administrator to even see broadly what was 
happening, and what workflow items *were* in process. We have a number of items 
that have been hanging out in that space, and this is the first time that I've 
actually been able to see them.

My hope is that I can work on cleaning those up, and then not have so many 
sitting around -- but I would find it very helpful to be able to check and 
export a CSV periodically, just to check in with folks who use the workflow 
setup.

Does that make sense as a use case?

Thanks again,
Paige

On Wed, Nov 30, 2022 at 15:36 Tim Donohue  wrote:
Hi Paige & Keith,

I can confirm this is happening locally for me as well.  It looks like a 
possible bug.  This "Export to CSV" works fine in normal search results & also 
in the "Your submissions" part of MyDSpace.  But, I can verify that it doesn't 
work when viewing "Workflow tasks".

That said, I admit, I wonder if that "Export to CSV" link should even appear on 
the "Workflow tasks" page, as it's not really possible to perform batch 
metadata editing on "Workflow tasks". (The Export to CSV feature is primarily 
used for Batch Metadata Editing purposes)

So, this is all to say, I think there's a bug here.  But, the bug might be that 
the option even appears on this page.  Is this a specific use case you had for 
wanting to export Workflow Tasks to CSV?  Just curious as maybe there's a way 
to get this possibly accidental feature "working" rather than remove it 
altogether.  Either way, I do think this is a bug, I'm just not sure which fix 
is appropriate yet (remove it, or fix it).

If you have time, please feel free to submit a bug ticket to 
https://github.com/DSpace/dspace-angular/issues   I'm assuming you likely want 
it "fixed" (rather than removed), so it'd be useful to understand your use 
cases in this ticket.

Thanks!

Tim

Tim

From: 

Re: [Extern] [dspace-tech] Submission: How to remove placeholder text from input fields

[Franziska Rapp]

Thanks Michael for you quick help.

Best regards
Franziska

Am 22.05.2024 um 14:18 schrieb Michael Plate:

Hi Franziska,

Am 22.05.24 um 13:23 schrieb Franziska Rapp:

Hi,

We would like to remove the placeholder text in the input fields 
during submission, e.g. "Author" in the Author field, "Title" in the 
Title field etc.


Which modifications do we need to make?

[…]

solution is CSS:

dynamic-ng-bootstrap-input input[type=text]::placeholder{
    opacity: 0 !important;
}

this is just for the standard text input (onebox), it works by setting 
the opacity of the placeholder to 0, so the placeholder is there, but 
not visible


solution in Typescript:

in your dspace-angular folder, open

src/app/shared/form/builder/ds-dynamic-form-ui/ds-dynamic-form-control-container.component.ts 



and in the ngOnInit function set the placeholder of the model to be 
empty:


[…]
ngOnInit(): void {

if( this.model.inputType=='text') {
  this.model.placeholder='';
 }
[…]

there are other places maybe…

CU

Michael


--
Franziska Rapp
Communication and Information Center (kiz)
Ulm University

--
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/3029b5cb-f642-4a69-8ecb-f421f507114f%40uni-ulm.de.