Hi Euler,

See the note at the top of the docs 
here: https://wiki.lyrasis.org/display/DSDOC7x/Google+Scholar+Metadata+Mappings

DSpace 7 doesn't support the "google-metadata.properties" file, but you can 
edit these mappings in the "metadata.service.ts" of the frontend codebase.  
Eventually we'd love to make them more easily configurable again, but it's 
not an easy task.  Nonetheless, we have a bug ticket for this 
here: https://github.com/DSpace/dspace-angular/issues/1198  It's waiting on 
a volunteer to claim it.

Tim

On Friday, January 26, 2024 at 4:24:47 AM UTC-6 euler wrote:

> Dear All,
>
> I noticed that whatever I added in the google-metadata.properties was not 
> picked up when I viewed the citation_ in the meta tags. For example, I 
> added this:
> google.citation_journal_title = dc.citation.journaltitle
> google.citation_volume = dc.citation.volume
> google.citation_issue = dc.citation.issue
> google.citation_firstpage = dc.citation.firstpage
> google.citation_lastpage = dc.citation.lastpage
> google.citation_doi = dc.identifier.doi
>
> It seems that only the default or original values in the 
> google-metadata.properties were being picked up in the meta tags. Is this a 
> bug or did I just miss something? I visited other sites that I know have 
> added their custom fields in the google-metadata.properties (by looking at 
> their DSpace forks, e.g. CGSpace, shout out to Alan Orth) and it seems that 
> theirs are also missing (e.g. https://hdl.handle.net/10568/137607). I 
> didn't have this issue in 6x.
>
> Thanks in advance!
> euler
>

-- 
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/46c2a927-dd41-467f-b0ff-69fcaf7e29a9n%40googlegroups.com.

Reply via email to