-
Notifications
You must be signed in to change notification settings - Fork 2
Context Menu
Every interface within the Repository View Context has a context menu. The context menu contains action in the following categories:
- Container Actions
- Resource Actions
- Admin Actions
Container action are available on all interfaces within the Repository View Context.
Clicking the start transaction option within the context menu will place the repository into transaction mode, indicated by a blue alert at the top of the page. When in transaction mode all changes made to the IR through CAP will can be rolled back.
Rolling back changes is accomplished by clicking the "rollback" button found in the transaction alert at the top of the page.
If you are happy with the changes you have made, you can commit these changes by clicking the "Commit" button in the transaction alert at the top of the page.
If you would like to roll back your transaction this can be done by clicking the "Rollback" button in the Transaction Alert. You will be presented with this confirmation modal.
Transactions have a limited duration. When the transaction has only 30n seconds remaining it will display a refresh button within the transaction alert. Clicking this button will result in the renewal of your transactions time. Allowing the time to lapse will result in the rollback of your transaction.
Selecting the "Versions" action from the context menu will result in the Versions Modal appearing. This modal consists of a "Cut New Version" input and button, as well as a list of historical versions of the current container or resource. In order to create a new version of the current container or resource, you can simply click the "Create" button under the "Cut New Version." This will result in the creation of a new version appearing in the list of historical versions with a autogenerated name. If it is desirable you can provide a name for a version by typing in the input field next to the create button. All version names will be prefixed with "version."
In order to view a version you can click on the "View" link on any entry in the Historical Version Table. This will place the Repository View Context into version mode.
When in version mode the state of the container or resource being viewed is identical to the state of IR at the time when the version was cut. In version mode the IR is not editable. Viewing a container or resource in version mode is indicated by an alert appearing at the top of the page. This alert contains to buttons: "Restore," which will replace the current the current state of the container or resource with the version being viewed; and "Delete," which will remove that historical version and return you to the current container or resource.
Currently the move, migrate and export options are disabled, as they have not yet been implemented in CAP.
Selecting the delete option from the context menu will result in this confirmation modal. Confirming deletion will remove the container or resource in question and return the user to the parent container.
Resource actions are those actions which can be performed solely when viewing a resource.
The fixity of the resource in question can be confirmed using the fixity action.
Clicking the fixity action will result in this modal. Clicking the check fixity button will result in a fixity check being run against the resource.
Once the check has been completed the results will be displayed within the fixity modal. The Message Digest is the fixity hash, and this can be copied to the clipboard via the clip board button at the end of the hash.
Clicking the download button will result in your system file location dialogue, giving you the opportunity to choose where the resource will be downloaded to.
Admin actions are action available for both resources and containers, but only for those users with administrative privileges.
The advanced query action results in the advanced query modal appearing. From this modal you can issue SPRQL queries directly against the IR. It is recommended that this feature be used with caution, as these queries are issued directly, with not validation.
This action returns the user to the administrative interface, where repository views and schemas may be managed.