Re: [dspace-tech] Migrating sharded SOLR statistics to DSPACE 7.4

[Sean Carte]

Hi Tuan

On the Slack tech-support channel, Nicholas Woodward reported that he had
recreated the cores 'by copying the new statistics core into a new Solr
configset, e.g. statistics-2022, for each previous year and changing the
schema name in schema.xml. Then after restarting Solr I was able to import
all of the old stats CSV files.'

I was about to try this, when I realised I'd made a mistake and imported
all my sharded statistics into the main core. I'm actually fine with that,
unless someone here tells me that that was a terrible thing to do.

Sean

On Tue, 14 Feb 2023 at 14:53, amtuan...@gmail.com 
wrote:

> Hi all
>
> We are in the process of migrating our DSpace 6x to 7.4.
>
> I am running into a problem with trying to import the SOLR statistics CSV
> files. We have our statistics sharded for each year and dumped the data to
> CSV files. However, the upgrade instructions have no mention of how to
> recreate the shards for statistics, only instructions for importing the
> CSVs. When I try to import the shards, I get the error 404 because the
> cores/shards are not created yet. Could you please give me some hints how
> to do this?
>
> Thanks for you help.
> Tuan
>
> https://wiki.lyrasis.org/display/DSDOC7x/Upgrading+DSpace
>
> Excerpt of the instructions I  followed below:
>
> Load authority and statistics from the dumps
> 
>  that
> you made earlier (not the disaster-recovery backup).
>
> [dspace]/bin/dspace solr-import-statistics -i authority
> [dspace]/bin/dspace solr-import-statistics -i statistics
>
> This could take quite some time.
>
> *If you had sharded your statistics, you will need to load the dump of
> each shard separately.  As when dumping, the index names will be ...
> statistics-2017 statistics-2018 statistics.*
>
> --
> 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/e2cc11bc-1761-4936-8a15-5895b3741340n%40googlegroups.com
> 
> .
>

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CA%2BxAuhM2EWcWn-05HU67xoCbAoJ7hqgJSugcfevYdtuzt9ymnQ%40mail.gmail.com.

[dspace-tech] Re: OAI SUPPORT

[Mohammad S. AlMutairi]

Also, Check Jakob's confirmation of how he solved his issue in his post.

 https://groups.google.com/g/dspace-tech/c/zgPQBcB4YWU/m/IXdt9mFGCQAJ

On Thursday, February 16, 2023 at 9:38:58 AM UTC+3 Mohammad S. AlMutairi 
wrote:

> Hi Nicolas,
>
> Just a suggestion. Double-check how the tomcat connector was installed. 
>
> # You need to replace the Catalina Connector Element on lines 69,70 and 71 
> with the connector settings you see below.
> 6) edit /etc/tomcat9/server.xml
> connectionTimeout="2"
>maxHttpHeaderSize="65536"
>minSpareThreads="25"
>enableLookups="false"
>disableUploadTimeout="true"
>URIEncoding="UTF-8"/>
>
>
> Hope it helps
>
> BR
>
> On Wednesday, February 15, 2023 at 9:10:57 PM UTC+3 Nicolas Battaglia 
> wrote:
>
>> Hello everyone!
>> I am trying to configure the oai server of my dspace 7. The url works 
>> fine /server/oai/request?verb=Identify but when I want to enter the records 
>> section it gives me an error. In the logs I see this: 
>> om.lyncode.xoai.dataprovider.exceptions.OAIException: 
>> org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 923; Invalid 
>> byte 2 of 4-byte UTF-8 sequence.
>>
>> It seems to be some coding configuration but I can't figure it out.
>>
>> On the other hand, I have to configure a set to be able to be harvested 
>> by the national repository system of t Argentina , and I managed to find 
>> the documentation or I don't know how to find it.
>> Any help or suggestion?
>>
>> thank you so much
>>
>

-- 
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/e02bd211-5835-40a6-bf32-3ba3911327ben%40googlegroups.com.

Re: [dspace-tech] Re: Excluding metadata from browse and search result - dspace 7.3

[Technologiczny Informator]

Then you're probably looking for a file discovery.xml in folder 
.../dspace/config/spring/api

Regards,
Mariusz

środa, 15 lutego 2023 o 17:48:30 UTC+1 WILLIAN VALMORBIDA napisał(a):

> Hi,
>
> I tried this. This configuration only removes the metadata from the index, 
> but doesn't remove the metadata (dc.contributor.*) shown in the search 
> results.
> I believe that this needs to be changed in some page, but I don't located 
> it.
>
> Thanks
> Willian
>
>
> Em qua., 15 de fev. de 2023 às 08:43, Technologiczny Informator <
> tif...@gmail.com> escreveu:
>
>> Have you tried changing the webui.browse.index.2 parameter in the 
>> dspace.cfg file?
>> In your case it should be:
>> webui.browse.index.2 = author:metadata:dc.creator:text
>> then rebuild the index.
>>
>> Regards,
>> Mariusz
>>
>> wtorek, 14 lutego 2023 o 19:57:20 UTC+1 WILLIAN napisał(a):
>>
>>> For a institutional reason, I have changed in the dspace to dc.creator 
>>> be a main author of the document and I have used dc.contributor as advisor 
>>> and another informations about the advisor. So, everything is fine a 
>>> exception that the dc.creator and dc.contributor.* seems as author in the 
>>> search and browse results. I desire that only dc.creator apear in the 
>>> result, but no one configuration tha I have tested does that in DSpace 7.3.
>>> Anybody knows how to exclude dc.contributor.* from search and browse 
>>> results?
>>>
>>> -- 
>> All messages to this mailing list should adhere to the Code of Conduct: 
>> https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "DSpace Technical Support" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to dspace-tech...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/dspace-tech/dc0321ed-28a4-49d1-a661-126289e393cen%40googlegroups.com
>>  
>> 
>> .
>>
>
> [image: http://www.univates.br] 

-- 
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/2e3793ab-6a6e-41d2-abac-570e064970dfn%40googlegroups.com.

[dspace-tech] Re: OAI SUPPORT

[Mohammad S. AlMutairi]

Hi Nicolas,

Just a suggestion. Double-check how the tomcat connector was installed. 

# You need to replace the Catalina Connector Element on lines 69,70 and 71 
with the connector settings you see below.
6) edit /etc/tomcat9/server.xml



Hope it helps

BR

On Wednesday, February 15, 2023 at 9:10:57 PM UTC+3 Nicolas Battaglia wrote:

> Hello everyone!
> I am trying to configure the oai server of my dspace 7. The url works fine 
> /server/oai/request?verb=Identify but when I want to enter the records 
> section it gives me an error. In the logs I see this: 
> om.lyncode.xoai.dataprovider.exceptions.OAIException: 
> org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 923; Invalid 
> byte 2 of 4-byte UTF-8 sequence.
>
> It seems to be some coding configuration but I can't figure it out.
>
> On the other hand, I have to configure a set to be able to be harvested by 
> the national repository system of t Argentina , and I managed to find the 
> documentation or I don't know how to find it.
> Any help or suggestion?
>
> thank you so much
>

-- 
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/22f1fa4a-531c-40a3-ab60-1773392bf899n%40googlegroups.com.

[dspace-tech] OAI SUPPORT

[Nicolas Battaglia]

Hello everyone!
I am trying to configure the oai server of my dspace 7. The url works fine
/server/oai/request?verb=Identify but when I want to enter the records
section it gives me an error. In the logs I see this:
om.lyncode.xoai.dataprovider.exceptions.OAIException:
org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 923; Invalid
byte 2 of 4-byte UTF-8 sequence.

It seems to be some coding configuration but I can't figure it out.

On the other hand, I have to configure a set to be able to be harvested by
the national repository system of t Argentina , and I managed to find the
documentation or I don't know how to find it.
Any help or suggestion?

thank you so much

-- 
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/CAJVJSdBRyr4j%3D3jfyS%3DjE8TerZY6Aw-gX1gKm-y2M4p8Ve8uBg%40mail.gmail.com.

Re: [dspace-tech] Re: Excluding metadata from browse and search result - dspace 7.3

[WILLIAN VALMORBIDA]

Hi,

I tried this. This configuration only removes the metadata from the index,
but doesn't remove the metadata (dc.contributor.*) shown in the search
results.
I believe that this needs to be changed in some page, but I don't located
it.

Thanks
Willian


Em qua., 15 de fev. de 2023 às 08:43, Technologiczny Informator <
tif...@gmail.com> escreveu:

> Have you tried changing the webui.browse.index.2 parameter in the
> dspace.cfg file?
> In your case it should be:
> webui.browse.index.2 = author:metadata:dc.creator:text
> then rebuild the index.
>
> Regards,
> Mariusz
>
> wtorek, 14 lutego 2023 o 19:57:20 UTC+1 WILLIAN napisał(a):
>
>> For a institutional reason, I have changed in the dspace to dc.creator be
>> a main author of the document and I have used dc.contributor as advisor and
>> another informations about the advisor. So, everything is fine a exception
>> that the dc.creator and dc.contributor.* seems as author in the search and
>> browse results. I desire that only dc.creator apear in the result, but no
>> one configuration tha I have tested does that in DSpace 7.3.
>> Anybody knows how to exclude dc.contributor.* from search and browse
>> results?
>>
>> --
> 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/dc0321ed-28a4-49d1-a661-126289e393cen%40googlegroups.com
> 
> .
>

-- 
 

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CAG2_CwAdJ33%2Bm27vPB2_PPR6NcRRVKETio7eacDiJ5WedUOdfA%40mail.gmail.com.

[dspace-tech] Re: Excluding metadata from browse and search result - dspace 7.3

[Technologiczny Informator]

Have you tried changing the webui.browse.index.2 parameter in the 
dspace.cfg file?
In your case it should be:
webui.browse.index.2 = author:metadata:dc.creator:text
then rebuild the index.

Regards,
Mariusz

wtorek, 14 lutego 2023 o 19:57:20 UTC+1 WILLIAN napisał(a):

> For a institutional reason, I have changed in the dspace to dc.creator be 
> a main author of the document and I have used dc.contributor as advisor and 
> another informations about the advisor. So, everything is fine a exception 
> that the dc.creator and dc.contributor.* seems as author in the search and 
> browse results. I desire that only dc.creator apear in the result, but no 
> one configuration tha I have tested does that in DSpace 7.3.
> Anybody knows how to exclude dc.contributor.* from search and browse 
> results?
>
>

-- 
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/dc0321ed-28a4-49d1-a661-126289e393cen%40googlegroups.com.