org.dspace.content.RelationshipMetadataValue Maven / Gradle / Ivy

Go to download
Show more of this group Show more artifacts with this name
Show all versions of dspace-api Show documentation
DSpace core data model and service APIs.
There is a newer version: 8.0
/**
 * The contents of this file are subject to the license and copyright
 * detailed in the LICENSE and NOTICE files at the root of the source
 * tree and available online at
 *
 * http://www.dspace.org/license/
 */
package org.dspace.content;

import org.apache.commons.lang3.builder.HashCodeBuilder;
import org.dspace.core.Constants;

/**
 * This class is used as a representation of MetadataValues for the MetadataValues that are derived from the
 * Relationships that the item has. This includes the useForPlace property which we'll have to use to determine
 * whether these Values should be counted for place calculation on both the native MetadataValues and the
 * Relationship's place attributes.
 */
public class RelationshipMetadataValue extends MetadataValue {

    /**
     * This property determines whether this RelationshipMetadataValue should be used in place calculation or not
     */
    private boolean useForPlace;

    /**
     * This property determines whether this RelationshipMetadataValue should be used in place calculation or not.
     * This is retrieved from Spring configuration when constructing RelationshipMetadataValues. This Spring
     * configuration is located in the core-services.xml configuration file.
     * Putting this property on true will imply that we're now mixing plain-text metadatavalues with the
     * metadatavalues that are constructed through Relationships with regards to the place attribute.
     * For example, currently the RelationshipMetadataValue dc.contributor.author that is constructed through a
     * Relationship for a Publication will have its useForPlace set to true. This means that the place
     * calculation will take both these RelationshipMetadataValues into account together with the normal
     * plain text metadatavalues.
     * On the other hand, the journal name, volume and issue number which are constructed through a
     * Relationship from a Publication to a journal issue will have its useForPlace set to false.
     * This would typically be set to false for any singular metadata, and for any relationship where no mixing
     * with plain text variables is applicable
     */
    public boolean isUseForPlace() {
        return useForPlace;
    }

    public void setUseForPlace(boolean useForPlace) {
        this.useForPlace = useForPlace;
    }

    @Override
    public boolean equals(Object obj) {
        if (obj == null) {
            return false;
        }
        if (! (obj instanceof RelationshipMetadataValue)) {
            return false;
        }
        final RelationshipMetadataValue other = (RelationshipMetadataValue) obj;
        if (this.isUseForPlace() != other.isUseForPlace()) {
            return false;
        }
        return super.equals(obj);
    }

    @Override
    public int hashCode() {
        return new HashCodeBuilder().append(getID()).append(isUseForPlace()).toHashCode();
    }

    /**
     * Retrieves the Relationship ID from which the current RelationshipMetadataValue is derived
     *
     * @return the relationship ID
     */
    public int getRelationshipId() {
        return Integer.parseInt(getAuthority().substring(Constants.VIRTUAL_AUTHORITY_PREFIX.length()));
    }
}