beacon file script

[floriangantner]

References

Add references/links to any related issues or PRs. These may include:

• Fixes #issue-number (if this fixes an issue ticket)

Description

Working state of our Script to generate beacon files of some identifier based on the beacon draft (https://gbv.github.io/beaconspec/beacon.html) (our implementation in dspace 5 was mentioned in some earlier PR #218)
Script for generating files according to the beacon standard (see https://gbv.github.io/beaconspec/beacon.html). It get all (visibile) entities of some identifier and prints them into one process result file or optionally dumps them in the handler log. The usage is mainly popular among GLAM-Systems using the gnd-identifier in the DACH-Area. The header lines can be configured in the configuration.

Instructions for Reviewers

This is mainly some working solution for institutions in the DACH-Area (Germany, Austria, Switzerland) , e.g. archives or libraries to generate beacon files with gnd-identifiers. Feel free to pick it up and modify to your needs.

List of changes in this PR:

• introduced new beacon script.
• It works over the whole site on discoverable entities.
• Identifier, main resolver and additional resolvers as well as the header lines can be configured in beacon.cfg

Include guidance for how to test or review your PR. This may include: steps to reproduce a bug, screenshots or description of a new feature, or reasons behind specific changes.

Checklist

This checklist provides a reminder of what we are going to look for when reviewing your PR. You need not complete this checklist prior to creating your PR (draft PRs are always welcome). If you are unsure about an item in the checklist, don't hesitate to ask. We're here to help!

• My PR is small in size (e.g. less than 1,000 lines of code, not including comments & integration tests). Exceptions may be made if previously agreed upon.
• My PR passes Checkstyle validation based on the Code Style Guide.
• My PR includes Javadoc for all new (or modified) public methods and classes. It also includes Javadoc for large or complex private methods.
• My PR passes all tests and includes new/updated Unit or Integration Tests based on the Code Testing Guide.
• If my PR includes new libraries/dependencies (in any pom.xml), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
• If my PR modifies REST API endpoints, I've opened a separate REST Contract PR related to this change.
• If my PR includes new configurations, I've provided basic technical documentation in the PR itself.
• If my PR fixes an issue ticket, I've linked them together.

[floriangantner]

aligned to 2023.02.02 Release