RE: [dspace-community] Specify the type of metadata

[Fitchett, Deborah]

Kia ora,

No, this can’t be specified in the metadata registry. The qualifier is more to 
clarify to humans what kind of data is intended eg dc.contributor.author vs 
dc.contributor.editor  or dc.identifier.isbn vs dc.identifier.doi, but there’s 
no validation performed on it.

You can define the submission form to validate specific fields based on a 
regular expression. There’s a little information about this in the submission 
form documentation at 
https://wiki.lyrasis.org/display/DSDOC7x/Submission+User+Interface

Deborah

From: dspace-community@googlegroups.com  On 
Behalf Of Chandrika Hebbar
Sent: Thursday, July 27, 2023 4:21 AM
To: DSpace Community 
Subject: [dspace-community] Specify the type of metadata

You don't often get email from 
chandrikahebba...@gmail.com. Learn why this 
is important

Caution: This email originated from outside our organisation. Do not click 
links or open attachments unless you recognize the sender and know the content 
is safe.

Hi Team,

While creating metadata in the metadata registry, is there any way to specify 
the type that metadata should take (for example String, Date, Number...). There 
is an option to specify values in the Qualifier. Is this meant for specifying 
the type of metadata (If so, what are the values it can take)?


Thank you.

Regards,
Chandrika Hebbar
--
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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to 
dspace-community+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-community/90173036-363b-4daa-86be-60fc259cdcefn%40googlegroups.com.



"The contents of this e-mail (including any attachments) may be confidential 
and/or subject to copyright. Any unauthorised use, distribution, or copying of 
the contents is expressly prohibited. If you have received this e-mail in 
error, please advise the sender by return e-mail or telephone and then delete 
this e-mail together with all attachments from your system."

-- 
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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-community+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-community/ME3PR01MB7524CF00A1E9C112DE6AD884C500A%40ME3PR01MB7524.ausprd01.prod.outlook.com.

[dspace-community] Re: Google Scholar indexing

[DSpace Community]

Hi,

It's very difficult for us to guess why Google Scholar isn't indexing your 
site.  It could be as simple as they haven't found the new domain name.  

But, it also could be that you haven't followed all the 
guidelines/recommendations we have for Search Engine Optimization in the 
documentation 
at https://wiki.lyrasis.org/display/DSDOC7x/Search+Engine+Optimization

There was also another email thread sent to this same dspace-community 
mailing list about problems someone else had with Google Scholar indexing.  
So, that may also be a resource for how to solve one common 
problem: 
https://groups.google.com/g/dspace-community/c/yxV1lomMRM4/m/qwHtUrTJDwAJ

If you are able to provide additional details about what is wrong, we may 
be able to help further.  But, hopefully it's one of the common problems 
that is listed above.

Tim

On Wednesday, July 26, 2023 at 6:24:35 AM UTC-5 Oleksandr Shershun wrote:

> Dear Community, some time ago you help us! We again need your help again!
>
> We have a problem with indexing our repository in Google Scholar.
>
> Our repository https://card-file.ontu.edu.ua/ was correctly indexed after 
> your help 2 years ago, all of the issues were in a Google Scholar search, 
> but now we couldn't find any issues. In 2022, we must change the domain 
> name due to organization renaming. In 2023 we changed the Dsapce platform 
> on ver. 7.4. What happened and how we or you could fix this bug?
>

-- 
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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-community+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-community/7921d6e9-bb37-431b-a2af-66fd718c2acen%40googlegroups.com.

[dspace-community] Re: Google Scholar

[Santiago Lo Coco]

Thank you, Tim!

On Wednesday, July 26, 2023 at 7:02:13 PM UTC+2 DSpace Community wrote:

> Hi Santiago,
>
> I receive regular updates from the Google Scholar team on DSpace indexing. 
> I tend to talk with them a few times a year & receive updates about any 
> common issues they've found with indexing DSpace sites.  They have never 
> mentioned that the date format in "citation_publication_date" is an issue.  
> If they ever do, we'd treat it as a bug and get it fixed.
>
> However, I can verify that the "citation_publication_date" field simply 
> uses the same date as your "dc.date.issued" metadata field on the Item.  
> So, if you modify the "dc.date.issued" that will change the value in your 
> "citation_publication_date" meta tag.   But, I do not believe that is 
> necessary for Google Scholar to index your site.
>
> Similarly, I've not heard of any issues with "citation_abstract_html_url" 
> being the handle.  This field takes its value from the "dc.identifier.uri" 
> metadata field on your Item.  So, if the Item has a different value in that 
> field, it will be used in the "citation_abstract_html_url".
>
> Overall, it is possible to modify the behavior of these Google Scholar 
> tags in DSpace 7.  But, you have to modify the behavior of the 
> corresponding "setCitation*Tag()" method in the "metadata.service.ts" file 
> in the UI.  You'd then need to recompile and restart the UI.  For instance, 
> here's the method that sets the "citation_abstract_html_url" tag value: 
> https://github.com/DSpace/dspace-angular/blob/main/src/app/core/metadata/metadata.service.ts#L286
>
> Tim
>
> On Wednesday, July 26, 2023 at 2:02:35 AM UTC-5 santilo...@gmail.com 
> wrote:
>
>> Also, `citation_date` is not formatted as required by Google. This is a 
>> problem? 
>>
>> I don't know if we have to follow the format "obligatorily":
>>
>> Provide full dates in the "2010/5/12" format if available; or a year 
>> alone otherwise.
>>
>> And the last question: it is okay for the citation_abstract_html_url to 
>> be a handle URL (handle.net), isn't it? 
>>
>> I really don't know why we are not indexed by Google.
>>
>> Sorry to bother you with all these questions.
>>
>> Regards,
>> Santiago.
>>
>> On Wednesday, July 26, 2023 at 8:51:57 AM UTC+2 Santiago Lo Coco wrote:
>>
>>> I fixed the problem by adding this line:
>>>
>>> proxy_set_header Host $host;
>>>
>>> Regards,
>>> Santiago.
>>>
>>> On Wednesday, July 26, 2023 at 8:34:30 AM UTC+2 Santiago Lo Coco wrote:
>>>
 Thank you Tim.

 The problem is that I already done that.

 This is my nginx config for the frontend:

 location / {
 proxy_set_header X-Forwarded-Proto https;
 proxy_set_header X-Forwarded-Host $host;
 proxy_set_header X-Forwarded-Server $host;
 proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
 proxy_pass http://localhost:4000;
 }

 Do you know if there is a mistake? 

 I also add some `add_header` directives for debugging and they are 
 working perfectly. 

 This is the output of `curl -v`:

 X-Forwarded-Host: repositorio.uflo.edu.ar
 X-Forwarded-Proto: https

 Regards,
 Santiago.
 On Tuesday, July 25, 2023 at 10:35:03 PM UTC+2 DSpace Community wrote:

> Hi Santiago,
>
> This sounds like this issue which is documented on our SEO guide in 
> the official docs: 
> https://wiki.lyrasis.org/display/DSDOC7x/Search+Engine+Optimization#SearchEngineOptimization-EnsureyourproxyispassingX-ForwardedheaderstotheUserInterface
>
> I suspect you need to add both X-Forwarded-Proto and X-Forwarded-Host 
> headers to your proxy.
>
> Tim
>
> On Tuesday, July 25, 2023 at 2:52:12 PM UTC-5 santilo...@gmail.com 
> wrote:
>
>> Hello,
>>
>> I am having a problem. For some reason, google scholar isn't indexing 
>> my website. The website generates almost all the *meta *tags 
>> perfectly. For example, with this article 
>> 
>> :
>>
>> 
>> 
>> 
>> 
>> 
>> 
>> https://hdl.handle.net/20.500.14340/909;>
>> 
>> https://localhost:4000/bitstreams/ea3094d6-1d9f-4c42-88aa-7bb038833f79/download
>> ">
>>
>> The only wrong tag and that is maybe the one that is causing the 
>> index to fail is the last one. How can I fix it? Because I can hardcode 
>> it 
>> in the frontend file but there must be a better solution. I am using a 
>> nginx proxy with the X-.. tags correctly. 
>>
>> Do you know if this is the problem causing google scholar to not 
>> index our website? 
>>
>> Regards,
>> Santiago.
>>
>>

-- 
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 

[dspace-community] Re: Google Scholar

[DSpace Community]

Hi Santiago,

I receive regular updates from the Google Scholar team on DSpace indexing. 
I tend to talk with them a few times a year & receive updates about any 
common issues they've found with indexing DSpace sites.  They have never 
mentioned that the date format in "citation_publication_date" is an issue.  
If they ever do, we'd treat it as a bug and get it fixed.

However, I can verify that the "citation_publication_date" field simply 
uses the same date as your "dc.date.issued" metadata field on the Item.  
So, if you modify the "dc.date.issued" that will change the value in your 
"citation_publication_date" meta tag.   But, I do not believe that is 
necessary for Google Scholar to index your site.

Similarly, I've not heard of any issues with "citation_abstract_html_url" 
being the handle.  This field takes its value from the "dc.identifier.uri" 
metadata field on your Item.  So, if the Item has a different value in that 
field, it will be used in the "citation_abstract_html_url".

Overall, it is possible to modify the behavior of these Google Scholar tags 
in DSpace 7.  But, you have to modify the behavior of the corresponding 
"setCitation*Tag()" method in the "metadata.service.ts" file in the UI.  
You'd then need to recompile and restart the UI.  For instance, here's the 
method that sets the "citation_abstract_html_url" tag 
value: 
https://github.com/DSpace/dspace-angular/blob/main/src/app/core/metadata/metadata.service.ts#L286

Tim

On Wednesday, July 26, 2023 at 2:02:35 AM UTC-5 santilo...@gmail.com wrote:

> Also, `citation_date` is not formatted as required by Google. This is a 
> problem? 
>
> I don't know if we have to follow the format "obligatorily":
>
> Provide full dates in the "2010/5/12" format if available; or a year alone 
> otherwise.
>
> And the last question: it is okay for the citation_abstract_html_url to 
> be a handle URL (handle.net), isn't it? 
>
> I really don't know why we are not indexed by Google.
>
> Sorry to bother you with all these questions.
>
> Regards,
> Santiago.
>
> On Wednesday, July 26, 2023 at 8:51:57 AM UTC+2 Santiago Lo Coco wrote:
>
>> I fixed the problem by adding this line:
>>
>> proxy_set_header Host $host;
>>
>> Regards,
>> Santiago.
>>
>> On Wednesday, July 26, 2023 at 8:34:30 AM UTC+2 Santiago Lo Coco wrote:
>>
>>> Thank you Tim.
>>>
>>> The problem is that I already done that.
>>>
>>> This is my nginx config for the frontend:
>>>
>>> location / {
>>> proxy_set_header X-Forwarded-Proto https;
>>> proxy_set_header X-Forwarded-Host $host;
>>> proxy_set_header X-Forwarded-Server $host;
>>> proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
>>> proxy_pass http://localhost:4000;
>>> }
>>>
>>> Do you know if there is a mistake? 
>>>
>>> I also add some `add_header` directives for debugging and they are 
>>> working perfectly. 
>>>
>>> This is the output of `curl -v`:
>>>
>>> X-Forwarded-Host: repositorio.uflo.edu.ar
>>> X-Forwarded-Proto: https
>>>
>>> Regards,
>>> Santiago.
>>> On Tuesday, July 25, 2023 at 10:35:03 PM UTC+2 DSpace Community wrote:
>>>
 Hi Santiago,

 This sounds like this issue which is documented on our SEO guide in the 
 official docs: 
 https://wiki.lyrasis.org/display/DSDOC7x/Search+Engine+Optimization#SearchEngineOptimization-EnsureyourproxyispassingX-ForwardedheaderstotheUserInterface

 I suspect you need to add both X-Forwarded-Proto and X-Forwarded-Host 
 headers to your proxy.

 Tim

 On Tuesday, July 25, 2023 at 2:52:12 PM UTC-5 santilo...@gmail.com 
 wrote:

> Hello,
>
> I am having a problem. For some reason, google scholar isn't indexing 
> my website. The website generates almost all the *meta *tags 
> perfectly. For example, with this article 
> 
> :
>
> 
> 
> 
> 
> 
> 
> https://hdl.handle.net/20.500.14340/909;>
> 
> https://localhost:4000/bitstreams/ea3094d6-1d9f-4c42-88aa-7bb038833f79/download
> ">
>
> The only wrong tag and that is maybe the one that is causing the index 
> to fail is the last one. How can I fix it? Because I can hardcode it in 
> the 
> frontend file but there must be a better solution. I am using a nginx 
> proxy 
> with the X-.. tags correctly. 
>
> Do you know if this is the problem causing google scholar to not index 
> our website? 
>
> Regards,
> Santiago.
>
>

-- 
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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-community+unsubscr...@googlegroups.com.
To view this discussion 

[dspace-community] Specify the type of metadata

[Chandrika Hebbar]

Hi Team,

While creating metadata in the metadata registry, is there any way to 
specify the type that metadata should take (for example String, Date, 
Number...). There is an option to specify values in the Qualifier. Is this 
meant for specifying the type of metadata (If so, what are the values it 
can take)?


Thank you.

Regards,
Chandrika Hebbar

-- 
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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-community+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-community/90173036-363b-4daa-86be-60fc259cdcefn%40googlegroups.com.

[dspace-community] Google Scholar indexing

[Oleksandr Shershun]

Dear Community, some time ago you help us! We again need your help again!

We have a problem with indexing our repository in Google Scholar.

Our repository https://card-file.ontu.edu.ua/ was correctly indexed after 
your help 2 years ago, all of the issues were in a Google Scholar search, 
but now we couldn't find any issues. In 2022, we must change the domain 
name due to organization renaming. In 2023 we changed the Dsapce platform 
on ver. 7.4. What happened and how we or you could fix this bug?

-- 
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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-community+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-community/21aecc28-a24e-49f4-b714-13fdd1a0dcaan%40googlegroups.com.

[dspace-community] Re: Google Scholar

[Santiago Lo Coco]

Also, `citation_date` is not formatted as required by Google. This is a 
problem? 

I don't know if we have to follow the format "obligatorily":

Provide full dates in the "2010/5/12" format if available; or a year alone 
otherwise.

And the last question: it is okay for the citation_abstract_html_url to be 
a handle URL (handle.net), isn't it? 

I really don't know why we are not indexed by Google.

Sorry to bother you with all these questions.

Regards,
Santiago.

On Wednesday, July 26, 2023 at 8:51:57 AM UTC+2 Santiago Lo Coco wrote:

> I fixed the problem by adding this line:
>
> proxy_set_header Host $host;
>
> Regards,
> Santiago.
>
> On Wednesday, July 26, 2023 at 8:34:30 AM UTC+2 Santiago Lo Coco wrote:
>
>> Thank you Tim.
>>
>> The problem is that I already done that.
>>
>> This is my nginx config for the frontend:
>>
>> location / {
>> proxy_set_header X-Forwarded-Proto https;
>> proxy_set_header X-Forwarded-Host $host;
>> proxy_set_header X-Forwarded-Server $host;
>> proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
>> proxy_pass http://localhost:4000;
>> }
>>
>> Do you know if there is a mistake? 
>>
>> I also add some `add_header` directives for debugging and they are 
>> working perfectly. 
>>
>> This is the output of `curl -v`:
>>
>> X-Forwarded-Host: repositorio.uflo.edu.ar
>> X-Forwarded-Proto: https
>>
>> Regards,
>> Santiago.
>> On Tuesday, July 25, 2023 at 10:35:03 PM UTC+2 DSpace Community wrote:
>>
>>> Hi Santiago,
>>>
>>> This sounds like this issue which is documented on our SEO guide in the 
>>> official docs: 
>>> https://wiki.lyrasis.org/display/DSDOC7x/Search+Engine+Optimization#SearchEngineOptimization-EnsureyourproxyispassingX-ForwardedheaderstotheUserInterface
>>>
>>> I suspect you need to add both X-Forwarded-Proto and X-Forwarded-Host 
>>> headers to your proxy.
>>>
>>> Tim
>>>
>>> On Tuesday, July 25, 2023 at 2:52:12 PM UTC-5 santilo...@gmail.com 
>>> wrote:
>>>
 Hello,

 I am having a problem. For some reason, google scholar isn't indexing 
 my website. The website generates almost all the *meta *tags 
 perfectly. For example, with this article 
 
 :

 
 
 
 
 
 
 https://hdl.handle.net/20.500.14340/909;>
 
 https://localhost:4000/bitstreams/ea3094d6-1d9f-4c42-88aa-7bb038833f79/download
 ">

 The only wrong tag and that is maybe the one that is causing the index 
 to fail is the last one. How can I fix it? Because I can hardcode it in 
 the 
 frontend file but there must be a better solution. I am using a nginx 
 proxy 
 with the X-.. tags correctly. 

 Do you know if this is the problem causing google scholar to not index 
 our website? 

 Regards,
 Santiago.



-- 
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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-community+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-community/8a321f20-4f73-4bf2-9b6e-af54325ce01cn%40googlegroups.com.

[dspace-community] Re: Google Scholar

[Santiago Lo Coco]

I fixed the problem by adding this line:

proxy_set_header Host $host;

Regards,
Santiago.

On Wednesday, July 26, 2023 at 8:34:30 AM UTC+2 Santiago Lo Coco wrote:

> Thank you Tim.
>
> The problem is that I already done that.
>
> This is my nginx config for the frontend:
>
> location / {
> proxy_set_header X-Forwarded-Proto https;
> proxy_set_header X-Forwarded-Host $host;
> proxy_set_header X-Forwarded-Server $host;
> proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
> proxy_pass http://localhost:4000;
> }
>
> Do you know if there is a mistake? 
>
> I also add some `add_header` directives for debugging and they are working 
> perfectly. 
>
> This is the output of `curl -v`:
>
> X-Forwarded-Host: repositorio.uflo.edu.ar
> X-Forwarded-Proto: https
>
> Regards,
> Santiago.
> On Tuesday, July 25, 2023 at 10:35:03 PM UTC+2 DSpace Community wrote:
>
>> Hi Santiago,
>>
>> This sounds like this issue which is documented on our SEO guide in the 
>> official docs: 
>> https://wiki.lyrasis.org/display/DSDOC7x/Search+Engine+Optimization#SearchEngineOptimization-EnsureyourproxyispassingX-ForwardedheaderstotheUserInterface
>>
>> I suspect you need to add both X-Forwarded-Proto and X-Forwarded-Host 
>> headers to your proxy.
>>
>> Tim
>>
>> On Tuesday, July 25, 2023 at 2:52:12 PM UTC-5 santilo...@gmail.com wrote:
>>
>>> Hello,
>>>
>>> I am having a problem. For some reason, google scholar isn't indexing my 
>>> website. The website generates almost all the *meta *tags perfectly. 
>>> For example, with this article 
>>> 
>>> :
>>>
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> https://hdl.handle.net/20.500.14340/909;>
>>> 
>>> https://localhost:4000/bitstreams/ea3094d6-1d9f-4c42-88aa-7bb038833f79/download
>>> ">
>>>
>>> The only wrong tag and that is maybe the one that is causing the index 
>>> to fail is the last one. How can I fix it? Because I can hardcode it in the 
>>> frontend file but there must be a better solution. I am using a nginx proxy 
>>> with the X-.. tags correctly. 
>>>
>>> Do you know if this is the problem causing google scholar to not index 
>>> our website? 
>>>
>>> Regards,
>>> Santiago.
>>>
>>>

-- 
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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-community+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-community/4b2a1962-6ca2-475f-8015-d55aed622fbfn%40googlegroups.com.

[dspace-community] Re: Google Scholar

[Santiago Lo Coco]

Thank you Tim.

The problem is that I already done that.

This is my nginx config for the frontend:

location / {
proxy_set_header X-Forwarded-Proto https;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-Server $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_pass http://localhost:4000;
}

Do you know if there is a mistake? 

I also add some `add_header` directives for debugging and they are working 
perfectly. 

This is the output of `curl -v`:

X-Forwarded-Host: repositorio.uflo.edu.ar
X-Forwarded-Proto: https

Regards,
Santiago.
On Tuesday, July 25, 2023 at 10:35:03 PM UTC+2 DSpace Community wrote:

> Hi Santiago,
>
> This sounds like this issue which is documented on our SEO guide in the 
> official docs: 
> https://wiki.lyrasis.org/display/DSDOC7x/Search+Engine+Optimization#SearchEngineOptimization-EnsureyourproxyispassingX-ForwardedheaderstotheUserInterface
>
> I suspect you need to add both X-Forwarded-Proto and X-Forwarded-Host 
> headers to your proxy.
>
> Tim
>
> On Tuesday, July 25, 2023 at 2:52:12 PM UTC-5 santilo...@gmail.com wrote:
>
>> Hello,
>>
>> I am having a problem. For some reason, google scholar isn't indexing my 
>> website. The website generates almost all the *meta *tags perfectly. For 
>> example, with this article 
>> 
>> :
>>
>> 
>> 
>> 
>> 
>> 
>> 
>> https://hdl.handle.net/20.500.14340/909;>
>> 
>> https://localhost:4000/bitstreams/ea3094d6-1d9f-4c42-88aa-7bb038833f79/download
>> ">
>>
>> The only wrong tag and that is maybe the one that is causing the index to 
>> fail is the last one. How can I fix it? Because I can hardcode it in the 
>> frontend file but there must be a better solution. I am using a nginx proxy 
>> with the X-.. tags correctly. 
>>
>> Do you know if this is the problem causing google scholar to not index 
>> our website? 
>>
>> Regards,
>> Santiago.
>>
>>

-- 
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 Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-community+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-community/564929ed-fae7-49d9-9185-9d452c32e226n%40googlegroups.com.