0.3.1 - Update version of "jackson-databind" to "2.8.11.2" to solve security issue

Same functionality as 0.3.0

About security issue (from GitHub Info)

• https://nvd.nist.gov/vuln/detail/CVE-2018-12022

CVE-2018-12022
More information
high severity
Vulnerable versions: >= 2.8.0, < 2.8.11.2
Patched version: 2.8.11.2

An issue was discovered in FasterXML jackson-databind prior to 2.7.9.4,
2.8.11.2, and 2.9.6. When Default Typing is enabled (either globally or
for a specific property), the service has the Jodd-db jar (for database
access for the Jodd framework) in the classpath, and an attacker can
provide an LDAP service to access, it is possible to make the service
execute a malicious payload.

0.3.0 - DSpaceSwordOnly, automatic support of different types of service document (collections/communities), "in-progress: true/false" as explicit variable

0.3.0 - 2019-03-05

Added

• usage of the Exporter-Commons library 0.4.0 as a dependency (see https://github.com/bwfdm/exporter-commons)
  • some methods have new names and input variables
    • exportNewEntryWithMetadataAndFile(String collectionURL, Map<String, List> metadataMap, File file, boolean unpackFileIfArchive)
    • createEntryWithMetadataAndFile(String collectionURL, Map<String, List> metadataMap, File file, boolean unpackZip, boolean inProgress)
• new class DSpaceSwordOnly, which provides a full functionality via only SWORD-v2 protocol. For that case some extra configuration of the DSpace repository is needed:
  • on the publication repository server open the sword-v2 configuration file: /dspace/config/modules/sword-server.cfg
  • set value: expose-communities = true (to offer in the service document a list of communities instead of collections, per default is "false")
  • restart the web server as usual to apply the changes
• automatic support of different types of the service document (with collections or with communities inside)
• explicit usage of "in-progress: true" and "in-progress: false" headers (as input variable for the export methods)
• usage of the HTTP-client which does not ignore the SSL. If you have some problems (e.g. some exceptions "input is not a X.509 certificate"), please see here:
  • https://stackoverflow.com/questions/4325263/how-to-import-a-cer-certificate-into-a-java-keystore

Deprecated

• none

Removed

• exportNewEntryWithFileAndMetadata (see "added" section above)

Fixed

• none

0.2.0 - Start to use Exporter-Commons, new ExportRepository interface

DSpace-Connector, 0.2.0

• start to use Exporter-Commons as a dependency
• new interface for communication, see ExportRepository interface for more details.
• Metadata are supported only as a Map (not as XML-file)
• the library ONLY STARTS the publication procedure, it is necessary to login to the publication repository later and confirm the publication there. It is realized via the DSpace option "In-progress: true", which is hard coded for now. Possibility to change this option will come in next releases.
• Currently implemented methods could be found in functionality.md
• Changes could be found in CHANGELOG.md

Add as dependency to pom.xml

<dependency>
	<groupId>com.github.bwfdm</groupId>
	<artifactId>dspace-connector</artifactId>
	<version>0.2.0</version>
</dependency>

Known bugs

• see previous releases.

0.1.0 - basic functionality is supported.

DSpace-Connector, 0.1.0

• basic functionality is supported, see PublicationRepository.java interface for more details.
• the library ONLY STARTS the publication procedure, it is necessary to login to the publication repository later and confirm the publication there. It is realized via the DSpace option "In-progress: true", which is hard coded for now. Possibility to change this option will come in next releases.
• description of the matadata should be done in a format of Map. Metadata as XML-file in ATOM-format is supported too, but was not tested well.

Add as dependency to pom.xml

<dependency>
	<groupId>com.github.bwfdm</groupId>
	<artifactId>dspace-connector</artifactId>
	<version>0.1.0</version>
</dependency>

Known bugs

• publication of metadata via XML-flie in ATOM-format does not analyse a header "In-progress", what means, that per default the value ""In-progress: false" is used. It causes an immediate publication of the ingest in the publication repository, or moving of the ingest to the review step (so known "workflow"), if the review procedure in the corresponded collection is activated. The bug fix should be done by SwordClient -> checking of "In-Progress:true" inside the "org.swordapp.client.SWORDClient.java" should be added, lines 464-468. As a possible solution could be a new line:
  http.addInProgress(options, deposit.isInProgress());