Quite often one needs to apply some changes to a large number of resources. Instead of using the <tt>Resource</tt> class which is synchronous. They are easier ways, which are asynchronous.

Quite often one needs to apply some changes to a large number of resources. Instead of using the <tt>Resource</tt> class which is synchronous. They are easier ways, which are asynchronous.

+

<!--T:3-->

With KDE 4.9 the [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk-core/html/group__nepomuk__datamanagement.html Nepomuk Datamanagement libraries] finally became public and allow clients to make large bulk changes to '''Nepomuk'''. In fact they are now the de facto method of modifying data. All other client libraries are now built on top of the Data Management library.

With KDE 4.9 the [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk-core/html/group__nepomuk__datamanagement.html Nepomuk Datamanagement libraries] finally became public and allow clients to make large bulk changes to '''Nepomuk'''. In fact they are now the de facto method of modifying data. All other client libraries are now built on top of the Data Management library.

−

== Includes and Libraries ==

+

== Includes and Libraries == <!--T:4-->

Since the datamanagement libraries are so prevalent, they come bundled together with the NepomukCore library.

Since the datamanagement libraries are so prevalent, they come bundled together with the NepomukCore library.

+

<!--T:5-->

The appropriate functions are included in the [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk-core/html/group__nepomuk__datamanagement.html <tt>Nepomuk/DataManagement</tt>] include file.

The appropriate functions are included in the [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk-core/html/group__nepomuk__datamanagement.html <tt>Nepomuk/DataManagement</tt>] include file.

−

== Jobs ==

+

== Jobs == <!--T:6-->

+

<!--T:7-->

Each Datamanagement function returns a <tt>KJob</tt> which performs the jobs and returns a signal on completion. These jobs are automatically started, and like all other <tt>KJob</tt>s they are automatically deleted on completion.

Each Datamanagement function returns a <tt>KJob</tt> which performs the jobs and returns a signal on completion. These jobs are automatically started, and like all other <tt>KJob</tt>s they are automatically deleted on completion.

−

=== Errors ===

+

=== Errors === <!--T:8-->

+

<!--T:9-->

While these jobs are quite easy to use, they have inbuilt error checking that verifies the domain, range and cardinality of the properties that are being changed. Therefore it is important to check the error code of the job when it returns. A better error message can be received via <tt>KJob::errorString</tt>

While these jobs are quite easy to use, they have inbuilt error checking that verifies the domain, range and cardinality of the properties that are being changed. Therefore it is important to check the error code of the job when it returns. A better error message can be received via <tt>KJob::errorString</tt>

Latest revision as of 14:06, 11 December 2012

Contents

Quite often one needs to apply some changes to a large number of resources. Instead of using the Resource class which is synchronous. They are easier ways, which are asynchronous.

With KDE 4.9 the Nepomuk Datamanagement libraries finally became public and allow clients to make large bulk changes to Nepomuk. In fact they are now the de facto method of modifying data. All other client libraries are now built on top of the Data Management library.

Each Datamanagement function returns a KJob which performs the jobs and returns a signal on completion. These jobs are automatically started, and like all other KJobs they are automatically deleted on completion.

While these jobs are quite easy to use, they have inbuilt error checking that verifies the domain, range and cardinality of the properties that are being changed. Therefore it is important to check the error code of the job when it returns. A better error message can be received via KJob::errorString