Change & Version Information¶
The following is a summary of changes and improvements to
eulfedora. New features in each version should be listed, with
any necessary information about installation or upgrade notes.
- Require a version of python-requests earlier than 2.9 (2.9 includes change to upload behavior for file-like objects that breaks eulfedora api uploads as currently handled in eulfedora).
- Tutorial updated to be compatible with Django 1.8 thanks to jaska @chfw.
- New class-based view
eulfedora.views.RawDatastreamView, equivalent to
- Access to historical versions of datastreams now available in
- Change checksum handling to cue Fedora to auto-generate checksums on ingest.
- Recommended: Fedora 3.7+ for automatic checksum support on ingest
This checksum change in this release is a work-around for a Fedora bug present in 3.8 (at least, possibly 3.7), where passing a checksum type with no checksum value results in in Fedora storing an empty checksum, where previously it would calculate and store a checksum. On ingest, if a checksum type but no checksum value is specified, no checksum information will be sent to Fedora (when checksum type and checksum value are both specified, they will be passed through to Fedora normally). If you have auto-checksumming configured in Fedora, then your checksums should be generated automatically. Note that auto- checksum functionality on ingest was broken until Fedora 3.7 (see https://jira.duraspace.org/browse/FCREPO-1047); if you are still using an older version of Fedora and need checksums generated at ingest, you should use eulfedora 1.1.
ReverseRelationnow includes an option for specifying a property to be used for sorting resulting items. Can also be specified for reverse relations autogenerated by
unittest2is now optional for testutils
- Use python
eulfedora.indexdata.viewsinstead of the simplejson that used to be included with Django
- Support for Fedora 3.8.
eulfedora.views.raw_datastream()to handle old Fedora datstreams with invalid content size.
Differentiating Fedora error messages in some versions of Fedora (somewhere after 3.4.x, applicable to at least 3.7 and 3.8, possibly earlier versions) requires that Fedora be configured to include the error message in the response, as described at https://groups.google.com/forum/#!topic/fedora-tech/PAv1LYWPW0k
API methods that previously returned a tuple of response content and the url now simply return the response object, which provides access to both content and url (among other information). Server and DigitalObject classes should behave as before, but API methods are not backward-compatible.
The API upload method filesize is limited by the system maxint (2GB on 32-bit OSes) due to a limitation with the Python len() method (possibly dependent on your Python implementation). If you need large file upload support on a 32-bit OS, you should use an earlier version of eulfedora.
- New script upload-test.py for testing upload behavior on your platform; also provides an example of an upload callback method. (Found in the scripts directory, but not installed with the module.)
- bugfix: relationship methods on
DigitalObjectnow recognize unicode as well as string pids as resources.
- bugfix: correction in detailed output for validate-checksum script when all versions are checked and at least one checksum is invalid
- bugfix: support HTTP Range requests in
eulfedora.views.raw_datastream()only when explicitly enabled
- A repository administrator can configure a script to periodically check content checksums in order to identify integrity issues so that they can be dealt with.
- A repository administrator will receive an email notification if the system encounters bad or missing checksums so that they can then resolve any integrity issues.
- A repository admin can view fixity check results for individual objects in the premis data stream (for objects where premis exists) in order to view a more detailed result and the history.
- Support for basic HTTP Range requests in
eulfedora.views.raw_datastream()(e.g., to allow audio/video seek in HTML5 media players)
- It is now possible to add new datastreams using
eulfedora.models.DigitalObject.getDatastreamObject()(in contrast to predefined datastreams on a subclass of
DigitalObject). Adding new datastreams is supported when ingesting a new object as well as when saving an existing object. This method can also be used to update existing datastreams that are not predefined on a DigitalObject subclass.
- Development requirements can now be installed as an optional requirement
of the eulfedora package (
pip install "eulfedora[dev]").
- Unit tests have been updated to use
- Provides a nose plugin to set up and tear down for a test Fedora Commons repository instance for tests, as an alternative to the custom test runners.
- Bugfix: don’t auto-create an XML datastream at ingest when the xml content
is empty (i.e., content consists of bootstrapped
- Bugfix: handle Fedora restriction of ownerId field length to 64 characters.
owner, will now warn and truncate the value to allow the object to be saved.
- New command-line script
fedora-checksumsfor datastream checksums validation and repair. See Scripts for more details.
DigitalObjectnow provides access to the Fedora built-in audit trail; see
audit_trail. Also provides:
eulfedora.views.raw_audit_trail(): Django view to serve out audit trail XML, comparable to
audit_trail_users: set of all usernames listed in the audit trail (i.e., any users who have modified the object)
ingest_user: username responsible for ingesting the object into Fedora if ingest is listed in the audit trail
Relationnow supports recursive relations via the option
- API wrappers have been updated to take advantage of all methods
available in the REST API as of Fedora 3.4 which were unavailable in
3.2. This removes the need for any SOAP-based APIs and the
- Minor API / unit test updates to support Fedora 3.5 in addition to 3.4.x.
- Bugfix: Default checksum type for
DatastreamObjectwas previously ignored when creating a new datastream from scratch (e.g., when ingesting a new object). In certain versions of Fedora, this could result in datastreams with missing checksums (checksum type of ‘DISABLED’, checksum value of ‘none’).
Previously, several of the REST API calls in
eulfedora.api.REST_APIsuppressed errors and only returned True or False for success or failure; this made it difficult to determine what went wrong when an API call fails. This version of
eulfedorarevises that logic so that all methods in
eulfedora.api.REST_APIwill raise exceptions when an exception-worthy error occurs (e.g., permission denied, object not found, etc. - anything that returns a 40x or 500 HTTP error response from Fedora). The affected REST methods are:
New custom Exception
eulfedora.util.ChecksumMismatch, which is a subclass of
eulfedora.util.RequestFailed. This exception will be raised if
modifyDatastream()is called with a checksum value that Fedora determines to be invalid.
addDatastream()is called with a checksum value but no checksum type, current versions of Fedora ignore the checksum value entirely; in particular, an invalid checksum with no type does not result in a
ChecksumMismatchexception being raised. You should see a warning if your code attempts to do this.
eulfedora.models.DigitalObject.index_data()and sample Solr schema to include a new field (dsids) with a list of datastream IDs available on the indexed object.
0.16.0 - Indexing Support¶
- Addition of
eulfedora.indexdatato act as a generic webservice that can be used for the creation and updating of indexes such as SOLR; intended to be used with
0.15.0 - Initial Release¶
- Split out fedora-specific components from
eulcore; now depends on