PDF Citation Cover Page and Bitstream Bundles

[Eric Montague]

Before generating a Citation Cover Page:
Item Bitstreams contains BUNDLE: ORIGINAL,
which is the original and only PDF.  
The name of this PDF appears on the Item page

as a link to download the PDF.

After generating a Citation Cover Page:
Item Bitstreams no longer has BUNDLE: ORIGINAL.
Instead, Item Bitstreams contains BUNDLE: PRESERVATION,
which is the original PDF without the Citation Cover Page,
and BUNDLE: DISPLAY which is the original PDF with the Citation Cover Page.
The problem is, now no PDF name appears on the Item page,
which makes it impossible to download the PDF.

Has anyone successfully generated a downloadable PDF which contains 

a Citation Cover Page?
I could not find any documentation on how to specify BUNDLE: DISPLAY 

as the downloadable PDF, or documentation to specify which BUNDLES

are downloadable and should appear as links on the Item page.

I am running DSpace 8.0 on Windows Server.

Any help will be appreciated.

- Eric Montague, Web Developer

[DSpace Technical Support]

Hi Eric,

If you are still having this issue, we may need more information about what you are using to "generate a Citation Cover Page".   DSpace's own Citation Page feature should not be *deleting* any content, as it dynamically adds a Citation Page at the time in which the download occurs: https://wiki.lyrasis.org/display/DSDOC8x/PDF+Citation+Cover+Page

So, I'm not sure I understanding what you are using, and how it could have deleted any content or bundles.  I think we need more information on what steps you've taken to generate the Citation Cover Page, etc.

Tim

[Eric Montague]

Hi Tim,

I'm using the second option - run the PDF Citation Coverpage Curation Task.
The Citation Cover Page was not being generated on-the-fly when the PDF was downloaded.

A closer reading of the documentation, 'then disseminate the pre-generated citation-version',
suggests that the user is expected to modify the Item bundles,
ie. upload the DISPLAY pdf into a newly created ORIGINAL bundle, which works, but is not ideal.

Here are my local.cfg settings:

#---------------------------------------------------------------#

#--------------CURATION SYSTEM CONFIGURATIONS-------------------#

#---------------------------------------------------------------#

# Configuration properties used solely by the Curation system   #

#---------------------------------------------------------------#

### Task Class implementations

plugin.named.org.dspace.curate.CurationTask = org.dspace.ctask.general.CitationPage = citationpage

plugin.named.org.dspace.curate.CurationTask = org.dspace.ctask.general.NoOpCurationTask = noop

plugin.named.org.dspace.curate.CurationTask = org.dspace.ctask.general.RequiredMetadata = requiredmetadata

plugin.named.org.dspace.curate.CurationTask = org.dspace.ctask.general.MetadataValueLinkChecker = checklinks

#---------------------------------------------------------------#

#------------CITATION COVER PAGE CONFIGURATIONS-----------------#

#---------------------------------------------------------------#

citation-page.enable_globally = true

citation-page.citation_as_first_page = false

# First row of header, perhaps put your institution/university name

# A comma separator will create a header with multiple sections on one line.

#citation-page.header1=DSpace Institution

citation-page.header1 = Digital Archive

# Second row of header, perhaps put your DSpace branded name, and url to your DSpace

# A comma separator will create a header with multiple sections on one line.

#citation-page.header2=DSpace Repository,http://dspace.org

citation-page.header2 = https://my-server

# Metadata fields to display on the citation PDF.

# Specify in schema.element.qualifier form, and separate fields by commas. If you want a horizontal line, use _line_

#citation-page.fields=dc.date.issued,dc.title,dc.creator,dc.contributor.author,dc.publisher,_line_,dc.identifier.citation,dc.identifier.uri

citation-page.fields=dc.title,dc.contributor.author,dc.rights,_line_,dc.identifier.uri

# Footer text, either some type of license/copyright info, or just letting them know where they got the document from.

# Any commas in this footer should be escaped (\,)

#citation-page.footer=Downloaded from DSpace Repository\, DSpace Institution's institutional repository

citation-page.footer=Downloaded from Digital Archive (my-server)

- Eric

PS. Somehow, in trying to get Citation Pages working, I've managed to 'corrupt' the access restrictions for all PDFs.
For some reason, PDFs are no longer downloadable by Anonymous users. I must be logged in as Administrator in order
to successfully download PDFs. But I'll create a separate posting for this 'access' issue.

--
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 visit https://groups.google.com/d/msgid/dspace-tech/4ca94956-b1c1-4aef-ad19-fe52c98e2b69n%40googlegroups.com.

[Eric Montague]

BTW. No content is being *deleted* when the Citation Page is generated
using the PDF Citation Coverpage Curation Task - instead, the PDF in the ORIGINAL Bundle
is preserved in the newly created PRESERVATION Bundle.

- Eric

On 12/19/2024 12:45 PM, DSpace Technical Support wrote:

--

[DSpace Technical Support]

Hi Eric,

Interesting. I was *not* aware this "CitationPage" curation task existed (or I forgot about it).  Looking at the code, it appears to be written to *move* the (original) file from ORIGINAL to PRESERVATION bundle, and then *create* the PDF coverpage version in the DISPLAY bundle.

https://github.com/DSpace/DSpace/blob/main/dspace-api/src/main/java/org/dspace/ctask/general/CitationPage.java

It does NOT appear that behavior is configurable.  And these bundles (DISPLAY and PRESERVATION) are *not* standard DSpace bundles that are used in the User Interface.  My best guess is this was a script that someone used for a highly customized version of DSpace which "understood" these DISPLAY and PRESERVATION bundles...but I'm not sure how that code made it back into "core" DSpace.

So, it appears to me that you'd either need to customize the User Interface to use these bundles, or customize the code of the "CitationPage" script to use different bundles, or find a different workaround.  The other option would be to use the "on the fly" cover page creation which is better supported.

Tim

[ERIC MONTAGUE]

Thanks Tim,

 

How exactly does one enable “on the fly” cover page creation?

What config parameters need to be set?

 

To view this discussion visit https://groups.google.com/d/msgid/dspace-tech/1a122185-615b-45a2-bc18-810071de5650n%40googlegroups.com.

[DSpace Technical Support]

Hi Eric,

To enable "on the fly" cover page creation, I believe you just have to set on of the "enable" settings listed on this page: https://wiki.lyrasis.org/display/DSDOC8x/PDF+Citation+Cover+Page   You can enable it globally for everything, or per Community/Collection.  Essentially, all you should need are the settings listed on that page.

Tim