Item page: Checksum rendering: Configure visibility

[bram-atmire]

Is your feature request related to a problem? Please describe.

In DSpace 10 the checksum for bitstreams is rendered on the item page. For most users, definitely anonymous users, it doesn't serve a specific use case and could be confusing or a waste of screen real estate

Describe the solution you'd like

Make this rendering configurable, with a config parameter allowing values such as:

• public
• admin-only
• hidden

Describe alternatives or workarounds you've considered

Removing the checksum rendering on item pages al together. Might belong for admins under "Administer" but not convinced that it immediately serves a wider purpose. If the file download just works, i'm not sure if any regular consumer/user would bother with the checksum.

[tdonohue]

NOTE: This display only appears if you have the new showDownloadLinkAsAttachment config set to true (the default value is false). See the description of that setting in the new "Layout settings" added in 10.0: https://wiki.lyrasis.org/spaces/DSDOC10x/pages/408944956/User+Interface+Configuration#UserInterfaceConfiguration-Layoutsettings

However, this is reproducible on demo.dspace.org and sandbox.dspace.org because we enable that configuration on those sites.

This ticket is loosely related to #5821 because they both describe behavior that only occurs when showDownloadLinkAsAttachment: true is set.

[tdonohue]

@bram-atmire : I realized this is already configurable via the advancedAttachmentRendering setting described at https://wiki.lyrasis.org/spaces/DSDOC10x/pages/408944956/User+Interface+Configuration#UserInterfaceConfiguration-Layoutsettings

By default, that setting will display specific metadata fields:

  # Configuration for advanced attachment rendering in item pages. This controls how files are displayed when showDownloadLinkAsAttachment is enabled.
  # Defines which metadata/attributes to display for bitstream attachments.
  advancedAttachmentRendering:
    # Metadata and attributes to display for each attachment
    metadata:
      - name: dc.title
        type: metadata
        truncatable: false
      - name: dc.type
        type: metadata
        truncatable: false
      - name: dc.description
        type: metadata
        truncatable: true
      - name: size
        type: attribute
      - name: format
        type: attribute
      - name: checksum
        type: attribute

As you can see, one of the settings above lists that the checksum will be displayed. However, if you remove checksum from this list, then it will no longer be displayed.

So, I believe this ticket can be closed out because the configuration already exists.

[bram-atmire]

Right, I guess there are 3 viable paths and I'm ok with all of them

• Just leave as is, close issue, and leave it up to the implementers to configure accordingly
• A two liner change where we just take out checksum from that config, so that the default becomes that it's not rendered
• my PR 5823 that adds the additional visibility config

[tdonohue]

@bram-atmire : I think I'd lean towards your first or second approaches here. I'm OK with removing the checksum config by default if we feel it really shouldn't be displayed by default. Sites who want it displayed can easily configure it back in.

Personally, I'm not sure about PR #5823, as I'm worried it may be "overkill" and may not correspond to any use case or need. Are their sites that would want to only display checksums to admins?

Overall, I admit, I don't have strong opinions on whether a checksum is displayed or not. For users who understand what a checksum is, displaying it could be perceived as "trustworthy" behavior from DSpace. But, if we feel it's not useful to most users (and I can understand that argument), then I'd be in favor of removing it from the default configuration and letting sites decide themselves if they want to enable it.