Projects/Nepomuk/BulkChanges - Revision history

AnneW: Marked this version for translation

2012-12-11T14:06:40Z

Marked this version for translation

AnneW: Preparing for translation

2012-12-11T14:06:30Z

Preparing for translation

Vishesh: Added examples

2012-08-24T10:12:48Z

Added examples

Vishesh: /* DataManagement */

2012-08-24T10:08:03Z

‎DataManagement

Vishesh: Initial commit

2012-08-22T09:41:04Z

Initial commit

New page

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

= DataManagement =

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 defacto method of modifying data. All other client libraries are now built on top of the Data Management library.

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

The appropriate functions are included in the <code>Nepomuk/DataManagement</code> include file.

==Jobs==

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

=== Errors ===

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 <code>KJob::errorString</code>

@@ Line 1: / Line 1: @@
 <languages />
 <translate>
-== Making Bulk Changes ==
+== Making Bulk Changes == <!--T:1-->
 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.
 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.
 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-->
 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-->
 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>
-== Examples ==
+== Examples == <!--T:10-->
 Setting the tags for a large number of resources -
 <syntaxhighlight lang="cpp-qt">
@@ Line 27: / Line 33: @@
      QVariantList tagResources;
-     KJob* job = setProperty( resourceList, NAO::hasTag(), tagResources );
+     <!--T:12-->
      connect( job, SIGNAL(result(KJob*)), this, SLOT(slotTagUpdateDone()) );
 </syntaxhighlight>
 This can also be done synchronously by running an event loop in the background -
 <syntaxhighlight lang="cpp-qt">
@@ Line 40: / Line 48: @@
 </syntaxhighlight>
 [[Category:Documentation]]
 [[Category:Development]]
 [[Category:Tutorials]]
 </translate>

@@ Line 1: / Line 1: @@
-Quite often one needs to apply some changes to a large number of resources. Instead of using the <code>Resource</code> class which is synchronous. They are easier ways, which are asynchronous.
+<languages />
-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 defacto method of modifying data. All other client libraries are now built on top of the Data Management library.
+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.
-= Includes and Libraries =
+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.
 Since the datamanagement libraries are so prevalent, they come bundled together with the NepomukCore library.
-The appropriate functions are included in the [http://api.kde.org/4.x-api/kdelibs-apidocs/nepomuk-core/html/group__nepomuk__datamanagement.html <code>Nepomuk/DataManagement</code>] 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 ==
-Each Datamanagement function returns a <code>KJob</code> which performs the jobs and returns a signal on completion. These jobs are automatically started, and like all other <code>KJob</code>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 ===
-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 <code>KJob::errorString</code>
+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>
-= Examples =
+== Examples ==
 Setting the tags for a large number of resources -
@@ Line 35: / Line 39: @@
          kError() << job->errorString();
 </syntaxhighlight>

@@ Line 3: / Line 3: @@
 = DataManagement =
-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 defacto 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 defacto method of modifying data. All other client libraries are now built on top of the Data Management library.
 == Includes and Libraries ==
 Since the datamanagement libraries are so prevalent, they come bundled together with the NepomukCore library.
-The appropriate functions are included in the <code>Nepomuk/DataManagement</code> 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 <code>Nepomuk/DataManagement</code>] include file.
 ==Jobs==