org.odpi.openmetadata.accessservices.subjectarea.server.services

Class SubjectAreaTermRESTServices

java.lang.Object

org.odpi.openmetadata.accessservices.subjectarea.server.services.SubjectAreaRESTServices

org.odpi.openmetadata.accessservices.subjectarea.server.services.SubjectAreaTermRESTServices

public class SubjectAreaTermRESTServices
extends SubjectAreaRESTServices

TheSubjectAreaTermRESTServices provides the server-side implementation of the SubjectArea Open Metadata Access Service (OMAS) for Terms. This interface provides term authoring interfaces for subject area experts.

Field Summary

Fields inherited from class org.odpi.openmetadata.accessservices.subjectarea.server.services.SubjectAreaRESTServices

oMRSAPIHelper

Constructor Summary

Constructors

Constructor and Description
SubjectAreaTermRESTServices() Default constructor

Method Summary

Modifier and Type	Method and Description
SubjectAreaOMASAPIResponse	createTerm(String userid, Term suppliedTerm) Create a Term The name needs to be specified - as this is the main identifier for the term.
SubjectAreaOMASAPIResponse	deleteTerm(String userid, String guid, Boolean isPurge) Delete a Term instance
SubjectAreaOMASAPIResponse	getTermByGuid(String userid, String guid) Get a Term
SubjectAreaOMASAPIResponse	updateTerm(String userid, String guid, Term suppliedTerm, boolean isReplace) Update a Term

Methods inherited from class org.odpi.openmetadata.accessservices.subjectarea.server.services.SubjectAreaRESTServices

getPossibleClassificationsForTerm, getPossibleRelationshipsForTerm, getRepositoryConnector, setOMRSAPIHelper, setRepositoryConnector

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

SubjectAreaTermRESTServices

public SubjectAreaTermRESTServices()

Default constructor

Method Detail

createTerm

public SubjectAreaOMASAPIResponse createTerm(String userid,
                                             Term suppliedTerm)

Create a Term The name needs to be specified - as this is the main identifier for the term. The name should be unique for canonical glossaries. This API does not police the uniqueness in this case. The qualifiedName can be specified and will be honoured. If it is specified then the caller may wish to ensure that it is unique. If this qualifiedName is not specified then one will be generated as GlossaryTerm concatinated with the the guid. Failure to create the Terms classifications, link to its glossary or its icon, results in the create failing and the term being deleted

Parameters:

userid - userid

suppliedTerm - term to create

Returns:

response, when successful contains the created term. when not successful the following Exception responses can occur

• UserNotAuthorizedException the requesting user is not authorized to issue this request.
• MetadataServerUncontactableException not able to communicate with a Metadata respository service.
• InvalidParameterException one of the parameters is null or invalid.
• UnrecognizedGUIDException the supplied guid was not recognised
• ClassificationException Error processing a classification
• FunctionNotSupportedException Function not supported
• StatusNotSupportedException A status value is not supported

getTermByGuid

public SubjectAreaOMASAPIResponse getTermByGuid(String userid,
                                                String guid)

Get a Term

Parameters:

userid - unique identifier for requesting user, under which the request is performed

guid - guid of the term to get

Returns:

response which when successful contains the term with the requested guid when not successful the following Exception responses can occur

• UserNotAuthorizedException the requesting user is not authorized to issue this request.
• MetadataServerUncontactableException not able to communicate with a Metadata respository service.
• InvalidParameterException one of the parameters is null or invalid.
• UnrecognizedGUIDException the supplied guid was not recognised
• FunctionNotSupportedException Function not supported

updateTerm

public SubjectAreaOMASAPIResponse updateTerm(String userid,
                                             String guid,
                                             Term suppliedTerm,
                                             boolean isReplace)

Update a Term

Status is not updated using this call.

Parameters:

userid - userid under which the request is performed

guid - guid of the term to update

suppliedTerm - term to be updated

isReplace - flag to indicate that this update is a replace. When not set only the supplied (non null) fields are updated.

Returns:

a response which when successful contains the updated term when not successful the following Exception responses can occur

• UnrecognizedGUIDException the supplied guid was not recognised
• UserNotAuthorizedException the requesting user is not authorized to issue this request.
• FunctionNotSupportedException Function not supported
• InvalidParameterException one of the parameters is null or invalid.
• MetadataServerUncontactableException not able to communicate with a Metadata respository service.

deleteTerm

public SubjectAreaOMASAPIResponse deleteTerm(String userid,
                                             String guid,
                                             Boolean isPurge)

Delete a Term instance

There are 2 types of deletion, a soft delete and a hard delete (also known as a purge). All repositories support hard deletes. Soft deletes support is optional. Soft delete is the default.

A soft delete means that the term instance will exist in a deleted state in the repository after the delete operation. This means that it is possible to undo the delete. A hard delete means that the term will not exist after the operation. when not successful the following Exception responses can occur

Parameters:

userid - userid under which the request is performed

guid - guid of the term to be deleted.

isPurge - true indicates a hard delete, false is a soft delete.

Returns:

a void response when not successful the following Exception responses can occur

• UnrecognizedGUIDException the supplied guid was not recognised
• UserNotAuthorizedException the requesting user is not authorized to issue this request.
• FunctionNotSupportedException Function not supported this indicates that a soft delete was issued but the repository does not support it.
• InvalidParameterException one of the parameters is null or invalid.
• MetadataServerUncontactableException not able to communicate with a Metadata respository service. There is a problem retrieving properties from the metadata repository.
• EntityNotDeletedException a soft delete was issued but the term was not deleted.
• GUIDNotPurgedException a hard delete was issued but the term was not purged