|
Content Explorer
The Content Explorer lets you review the content of the CRX repository. The Content Explorer offers the following functions:
| Explorer pane |
Displays a tree of all the nodes in the repository. Click a node to display its contents in the node contents pane. After clicking a node, you can select an action in the toolbar. |
| Node contents pane |
Displays the properties and child nodes of the currently selected node. Click an item to display the details in the detail pane. After clicking an item, you can select an action in the toolbar. |
| Details pane |
Details of the item you have selected (see below). |
| Save all |
Saves all the changes you have made. Until you click save, the changes are temporary, and will be lost when you exit the console. |
| Refresh all |
Refreshes all the nodes. Changes from other users are updated in your view of the repository. Changes you have made are unaffected. |
| Revert all |
Discards all changes that you have made since you have saved last, and loads the current state of the repository. |
| Node |
This menu contains all the actions you can perform on the node level, such as adding nodes, moving nodes, and locking nodes. |
| Property |
This menu allows you to add and edit properties. |
| Versions |
Allows you to manage versions. Note that the version information is not stored with the data itself, but is in a separate part of the repository. If you export and re-import data, the version information may be lost. |
| Mixins |
Allows you to add so-called mixin types to the node type. The mixin types are mostly used to add advanced features such as versioning, access control, referencing, and locking to the node. |
| Security |
Allows you to set permissions on the currently selected node and set user passwords. |
| Search |
Opens the search window, where you can search the repository content using powerful search queries. |
| Workspace |
The Clone function allows you to copy a branch from another workspace into the workspace that is currently displayed. The function takes four arguments: - The name of the source workspace, for example "default." - The path of the source node, for example "/myNode." - The path of the target node you want to create, for example "/myTargetNode." If the node exists, CRX creates a same-name sibling. - Whether you want to overwrite existing UUIDs. Type true to remove existing nodes with the same UUID as a node you want to copy. If you type false, CRX fails if it encounters existing UUIDs.
Note: CRX copies the source node and all nodes below it, so that the target node becomes the copy of the source node. |
| View |
Changes the detail level and settings of the Content Explorer. |
The node details are displayed in the details pane after you have clicked a node. They contain all the settings of the node.

| Name |
The name of the node. |
| Primary Node Type |
The primary node type. Every node has a primary type, which defines the structure of the node's properties and child nodes. The node type nt:unstructured does not place any restrictions on properties or child nodes. You can use other node types to enforce a very strict structure of your data. |
| Path |
The path of the node. |
| UUID |
The unique universal identifier of the node.This is used to locate the node independent of the path, so CRX can track its location if you move it. The UUID is used for references. The node receives a UUID when you assign the mixin type mix:referenceable. |
| Depth |
The hierarchical depth of the node in the tree. |
| Is New |
True if the node is newly created and has not been saved yet. |
| Is Modified |
True if the node has been modified, and the modifications have not been saved yet. |
| Is Locked |
True if the node is locked by an application. Note that CRX and the Content Explorer do not lock nodes while you work on them. If you write an application that requires locking, the application has to set and remove the locks. In order to lock a node, the node must have the mixin type mix:lockable. |
| Is Checked Out |
True if the node is currently checked out. Checkout is possible only if the node is versionable. For this, assign the mixin type mix:versionable to the node type. Now a version of the node is saved in the version storage every time you check in the node. Note that checkout does not automatically lock the node. |
| Holds Lock |
True if the node holds the lock on its entire subtree. If true, and if the node is locked, then you cannot change any of the node's properties or child nodes. If false, the lock is limited to the current node. |
| Super Types |
The node type that this node type is based upon. If nothing else, a node type is based on nt:base, which does not place any restrictions on the node type, except that is must have a primary type and may have mixin types. |
| Mixin Node Types |
The mixin node types used to add storage and behavior to primary node types. For example, if you add the mixin type mix:referenceable, the node receives a property named jcr:uuid, which contains the node's unique identifier. |
The Node menu allows you to perform several actions on the node you have selected in the Content Explorer.
| New Node |
Creates a new node below the node you have selected. |
| Refresh |
Refreshes the selected node. Changes from other users are updated in your view of the repository. Changes you have made are unaffected. |
| Revert |
Discards the changes that you have made to the node since you have saved last, and loads the current state of the node from the repository. |
| Save |
Saves the changes to one node. Note that in some instances, you cannot save a node due to logical implications. For example, you cannot save a child node of a node that has not been saved before. |
| Move |
Moves the node and all nodes below it to a new location. A window opens where you can specify the target node. |
| Copy |
Copies the node and all nodes below it to a new location. A window opens where you can specify the target node. |
| Update |
If the node has a corresponding node in another workspace, the update command replaces the node, its child nodes, and its properties with the node, child nodes, and properties from the other workspace. The update command takes one argument, the name of the workspace from which you want to update.
There are two ways in which a node can have a corresponding node: - If the node has a UUID, the corresponding node is the node in the other workspace that has the same UUID.- If the node has no UUID, the corresponding node is the node with the same path to the next parent with the same UUID. |
| Merge |
The merge command is an extended update command that respects versioning. The merge command follows a complex algorithm to determine which of the child nodes are updated or versioned. See the JSR-283 specification for details. |
| Edit |
Edits the primary property of a node. |
| Delete |
Deletes the node. If deleting large node trees, select Delete Recursively. |
| Delete Recursively |
Deletes large node trees by breaking up commits into smaller chunks. |
| Restore |
Restores a version of a node. You need the full path of the version in the version storage. The path contains the following parts: - The path of the version storage, which is “/jcr:system/jcr:versionStorage”. - The UUID of the version history node. Click the node, then click the Versions menu, and click Version Graph. Open the jcr:frozenNode folder; the UUID is in the field jcr:versionHistory. - The name of the version, for example "1.0."
For example, a path may look as follows:
/jcr:system/jcr:versionStorage/eaaf3ca0-6c4b-4197-9936-dd68bf7bd9c7/1.0
Note that you can also restore a node directly in the Version Graph window. |
| Lock |
Locks the node. After you click Lock, only you can make changes to the node. The lock expires when you click Unlock or when you log off. |
| Lock Deep |
Locks the node. After you click Lock, only you can make changes to the node or the sub nodes of the node. The lock expires when you click Unlock or when you log off. |
| Unlock |
Unlocks a locked node. Note that when you log off, all the nodes you have locked are automatically unlocked. |
| Replicate |
Adds the node to the replication queue. After replication, the node is added to the target repository. |
| Replicate Removal |
Adds a request to delete the node to the replication queue. After replication, the node is removed from the target repository. |
The Property menu allows you to add, modify, and delete properties.
| New property |
Adds a property to the selected node. |
| Refresh |
Refreshes the selected property. Changes from other users are updated in your view of the repository. Changes you have made are unaffected. |
| Revert |
Discards the changes that you have made to the property since you have saved last, and loads the current state of the node from the repository. |
| Save |
Saves the changes to the property. |
| Edit |
Allows you to edit the content of the property. |
| Delete |
Deletes the property. |
The Versions menu allows you to version nodes in the repository. Note that these functions are available only for nodes that have the mixin type "versionable."
| Check In |
Saves the current state of the node as a new version of the node in the version storage. You cannot modify the node while it is checked in. |
| Check Out |
Makes the node available for editing again. The changes you make to the node are not versioned until you check the node in. |
| Restore Base |
Restores the last versioned state of the node. Changes you have made since you have checked out the node are lost. |
| Done Merge |
A merge command may require manual changes before you can save the merge result. If so, and if you have made the changes, click Done Merge to apply the changes and the merge command. |
| Cancel Merge |
A merge command may require manual changes before you can save the merge result. Click Cancel Merge to cancel the merge command without saving the merge result. The repository is now in the same state that it was before you attempted the merge command. |
| Version Graph |
Opens a graph that shows the available versions of the node. This allows you to view and restore earlier versions of the node, and to label the existing versions |
Click the Mixins button to open the Mixin node type menu. This allows you to add so-called “mixin” node types. These types are used to add functions to a node, such as versioning or locking. To add a function to a node, add the corresponding mixin type. CRX then adds the properties and sub nodes required for this function.
The Security menu lets you to set passwords and access rights for the nodes in a workspace.
| Change Password |
To set the current user password select Security, and then Change Password. |
| Access Control Editor |
To add or remove access rights to a node, click the node, and then select Security, then Access Control Editor. See Access Right Management. |
User Administration
|
To manage user accounts select Security, and then User Administration. See User Administration.
|
| Group Administration |
To manage user accounts select Security, and then Group Administration. See Group Administration. |
The search window allows you to search the content of the current workspace, using either keywords, an SQL search query, or an XPath search query.
| Search for |
Type one or more keywords you want to search for. |
| Search in |
Type the path under which you want to search. Use the slash (“/”) to search the entire workspace. |
| Type |
The type of the search, either SQL or XPath. |
| Search now |
Click to execute the search query below. |
| Query |
The current search query. If you edit any of the fields above, the query changes to reflect the search you have specified. You can also type the search query directly in this field. |
| Results |
The list of search results. |
|
|
It's possible to obtain crx sql documentation with any exacts examples and their syntaxes beacause I have
a problem which don't allows me to resolve difficulty between date and comparison ...
Best regards,
Brice
I'm not sure I understand what the problem is. What documentation are you trying to get? What do you mean by date and comparison?
please send some suggestion.......
Note: Customers with DayCare user accounts need to create a new account for use on day.com.