The Bulk Editor allows for very efficient editing when the visual page context is not needed as it lets you:
- search for (and display) content from multiple pages; this is done using GQL (Google Query Language)
- edit this content directly in the bulk editor
- save the changes (to the originating pages)
- export this content to a tab-separated (.tsv) spreadsheet file
You can also import content into the repository, but by default this is disabled for the Bulk Editor as available in the Tools console.
This section describes how to work with the bulk editor in the Tools console. Typically, administrators use the bulk editor to search and edit multiple items. This is done by populating the table using a GQL query and then by selecting the content items to work on. Authors generally use the bulk editor as part of a customized bulk editor application accessible through the product listing component.
For example, if you need all the names and email addresses of users who filled out a particular survey, the Bulk Editor can provide that information and you can export it into a spreadsheet.
An example to illustrate such a use case is included in the Geometrixx web site:
Field Property Root Path Indicates the root path the bulk editor searches.
For example, /content/geometrixx/en. The bulk editor searches over all child nodes.
Query Parameters Using GQL parameters, enter the search string you want the bulk editor to look for in the repository; for example, type:Page looks for all pages in the root path, text:professional looks for all pages that have the word "professional" in them, and "jcr:title":English looks for all pages that have "English" as the title. You can only search for strings. Content Mode check box Select this check box to read properties within the jcr:content sub node of the search results if exists. Use for pages only. Property names are prefixed with "jcr:content/" Properties/Columns Select the check boxes for the properties that you want the bulk editor to return. The properties you select are the column heads in the results pane. By default, the node path is displayed in the results. Custom Properties/Columns Enter any other properties that are not listed in the Properties/Columns field. These custom properties appear in the results pane. You can add multiple properties by using a comma to separate properties. Note: If you add a custom property that does not yet exist, AEM WCM displays an empty cell. When you modify the empty cell and save it, the property is added to the node. The newly created property must respect node type constraints and property namespaces.
- path: only search nodes below this path. If you specify more than one term with a path prefix, only the last one will be considered.
- type: only return nodes of the given node types. This includes primary as well as mixin types. You may specify multiple comma separated node types. GQL will return nodes that are of any of the specified types.
- order: order the result by the given properties. You may specify multiple comma separated property names. To order the result in descending order simply prefix the property name with a minus. E.g.: order:-name. Using a plus sign will return the result in ascending order, which is also the default.
- limit: limits the number of results using an interval. E.g.: limit:10..20 Please note that the interval is zero based, start is inclusive and end is exclusive. You may also specify an open interval:limit:10.. or limit:..20 If the dots are omitted and only one value is specified GQL will return at most this number of results. E.g. limit:10 (will return the first 10 results)
You may need to export content and make changes to it in an Excel spreadsheet. For example, you may want to export a mailing list and change the area code of all the listed phone numbers directly in Excel, add additional lines, and so on.
Click Export to export the changes into a tab-separated Excel spreadsheet. AEM WCM asks you where you want to download the file.
By default, changes are encoded in Windows-1252 (also known as CP-1252). You can check UTF-8 to export the changes in UTF-8.
By default the import functionality is hidden when you open the Bulk Editor. Simply adding the parameter hib=false to the URL will display the Import button on the Bulk Editor page. You can import content from any tab-separated (.tsv) file. In order for importing to work properly, the column headings (first row of cells) must match the column headings of the table you are importing to.
When you re-import content, you erase any previous content for those nodes. Be careful not to overwrite important information.