Hello everyone,
just a small note regarding the discussion: we already talked about the
topic of bitstreams in the TEXT bundle in a developer meeting last year.
This resulted in the GitHub ticket
https://github.com/DSpace/DSpace/issues/11681.
Presumably, we can restrict access to the bitstreams in the TEXT bundle.
Ideally, the URLs should not appear in the SSR output at all.
Best
Sascha
Am 04.02.26 um 01:37 schrieb Andrew K:
I confirm this issue in 9.1
Sometimes Google Scholar indexes .pdf.txt files extracted from the
original .pdf
Everything as described.
середа, 4 лютого 2026 р. о 01:19:02 UTC+2 Bill Tantzen пише:
for example,
see https://conservancy.umn.edu/items/8cbfee50-2287-49d7-
a619-0a6bcdf0b7f8 <https://conservancy.umn.edu/
items/8cbfee50-2287-49d7-a619-0a6bcdf0b7f8>
search the source for 5cf5fe66-0954-4c8e-839c-cbef34394347, and
extracted text bitstream. it is in the <script> element.
It can be found in google scholar at
https://scholar.google.com/scholar?
hl=en&as_sdt=0%2C24&q=%22MINNESOTA+GEOLOGICAL+SURVEY+DAVID+L.
+SOUTHWICK%2C+DIRECTOR+BULLETIN+48+FREDERICK+WILLIAM+SARDESON%2C+GEOLOGIST%22&btnG=
<https://scholar.google.com/scholar?hl=en&as_sdt=0%2C24&q=%22MINNESOTA+GEOLOGICAL+SURVEY+DAVID+L.+SOUTHWICK%2C+DIRECTOR+BULLETIN+48+FREDERICK+WILLIAM+SARDESON%2C+GEOLOGIST%22&btnG=>
--
All messages to this mailing list should adhere to the Code of Conduct:
https://lyrasis.org/code-of-conduct/
---
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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/dspace-tech/05f30577-375f-45dc-bc9d-c2f6f9bf44fe%40hsu-hh.de.
