Ifd:updateConcept

API version 2
public IfdConcept updateConcept (IfdConcept concept, String session_id ) throws IfdServerException

Function to update a concept. Everything except GUID may be updated.

Input:
 * - Concept to be updated, any change to the GUID will be ignored.
 * session_id - The session id for the active user

Returns:
 * IfdConcept - The updated concept.

API version 3
public IfdConcept updateConcept (                                 String session_id,                                  IfdConcept concept) throws IfdServerException

EXPRESS Heading QUERY_FUNCTION updateConcept(                      concept : IfdConcept): IfdConcept;

The function update basic attributes of the specified concept.

Input: IfdConcept concept - specifications of the concept to be updated:
 * session_id - The session id for the active user
 * guid – global unique id of the target concept;
 * version_id – (optional) new version number of the concept. It shall be string with an integer * * value – new number of the version. If the value is the same as before it will be incremented by one. If the attribute is unset concept version will be unset;
 * version_date – ignored in input (concept after successive update will be set with current date/time stamp);
 * status – (optional) one of the following: 'DRAFT', 'CHECKED', 'APPROVED', 'INVALID', if unset – status of the concept will be left without changes;
 * concept_type – (optional) type for the updated concept, it shall be one of the following: 'ACTOR' 'ACTIVITY' 'BAG' ‘CONTEXT’ 'DOCUMENT' 'MEASURE' 'NEST' 'PROPERTY' 'SUBJECT' 'UNIT' 'VALUE' . if concept_type unset or the same as original – type of the concept will be left without changes;
 * full_names – ignored in the input, use addNamesToConcept, removeNameFromConcept, updateName or correctSpellingForName;
 * short_names – ignored in the input, use addNamesToConcept, removeNameFromConcept, updateName or correctSpellingForName;
 * lexemes – ignored in the input, use addNamesToConcept, removeNameFromConcept, updateName or correctSpellingForName;
 * definitions – ignored in the input, use addDefinitionsToConcept, removeDefinitionFromConcept, updateDefinition or correctSpellingForDescription;
 * comments – ignored in the input, use addCommentsToConcept, removeCommentFromConcept, updateComment or correctSpellingForDescription;
 * illustrations – ignored in the input, use addIllustrationsToConcept, removeIllustrationFromConcept;
 * owner – (optional) specified by guid organization which shall maintain the concept. If unset the home organization of the logged user is used;

Returns:
 * IfdConcept - Fully specified (in all available languages) updated concept.

Difference with v.2.00
 * (142)	In v.2.00 the function did not care about difference in type when moved original relationships to updated concept. That could makes IFD population invalid against ISO 12006-3 constraints;
 * (143)	In v.2.00 version of the concept in all updates just raised on 1, regardless of input version_id value. Current version do the same for invalid (not integer) input of the parameter in another case user can provide arbitrary versioning management

Comments: