File Reservation (Check-in/Check-out)
Table of contents
- 1. Introduction
- 1.1. Purpose
- 1.2. Intended Audience
- 1.3. Additional information
- 1.4. References
- 2. Status
- 3. Functional Specification
- 3.1. Use Cases
- 3.1.1. User discovers files that they have reserved
- 3.1.2. User discovers subscriptions to reserved files they have created
- 3.1.3. User reserves file
- 3.1.4. Users want to be notified of a file check-in
- 3.1.5. Users want to cancel notifications for file check-in
- 3.1.6. User lifts reservation on file with changes
- 3.1.7. User (or administrators) lifts reservation on file without changes
- 3.1.8. User lifts reservation on file by submitting any file
- 3.1.9. User wants to download a reserved file
- 3.1.10. User overwrites a reserved file
- 3.2. Non-goals
- 3.1. Use Cases
- 4. Technical Specification
- 4.1. Implications in Core & commercial:
- 4.2. UI requirements
- 4.3. API requirements
- 4.3.1. Extension Data Types
- 4.3.1.1. Reservation
- 4.3.2. Extension Features
- 4.3.2.1. GET:reservations
- 4.3.2.2. GET:reservations/{fileid}
- 4.3.2.3. PUT:reservations/{fileid}
- 4.3.2.4. DELETE:reservations/{file}
- 4.3.2.5. GET:reservations/{fileid}/subscriptions/currentuser
- 4.3.2.6. PUT:reservations/{fileid}/subscriptions/currentuser
- 4.3.2.7. DELETE:reservations/{fileid}/subscriptions/currentuser
- 4.3.2.8.
- 4.3.2.9. GET:subscriptions/{userid}
- 4.3.1. Extension Data Types
Introduction
While MindTouch has strong merging capabilities on content stored as MindTouch pages, the ability to collaborate through files is limiting due to the lack of document management tools.
Purpose
File reservation, a lightweight check-in/check-out workflow, forced through UI/social constructs (as opposed to actual file locks) will provide a feature that will allow users to know when a file has been "reserved" to prevent overwrites and multiple uploads.
Intended Audience
Deployments of MindTouch which require simple document management features.
Additional information
Project came in through a professional service contract. This module, once completed, will be available in commercial editions of MindTouch. It will require the Noatak release platform to function fully, although it will be installable on Minneopa (9.08) with some custom modifications.
Status
Functional spec is frozen; feature has been accepted into the Noatak release and is under active development.
Functional Specification
This feature enables the reservation of files attached to MindTouch pages by providing a visual and email notifications to interested users on the system. The purpose is to allow a user to place a reservation on a specific file while they are in the process of editing and/or creating a new version of the document. This process will not lock or prevent other users from accessing the file. Users visiting a page will see a visual cue that another user has reserved the file and may be in the process of editing.
Upon the uploaded a new version of the document the reservation is automatically removed showing the document as available for new reservations. Implementation of this functionality would not prevent concurrent edits being made by multiple users to a single document but would assist in preventing users from editing documents that were already in use by another user.
Use Cases
User discovers files that they have reserved
- User goes to a page which lists all files that are reserved by the current user
- Administrators can discover files that have been checked out within a system to do a "cleanup"
User discovers subscriptions to reserved files they have created
- User goes to a page which lists all the file reservations they have subscribed to
- Users can navigate to those pages to cancel subscriptions or cancel the reservation in place
User reserves file
- User navigates to the "files" section of a page and selects from the dropdown menu of actions, "Reserve"
- This launches a dialog which asks for confirmation that the user wishes to check out a file, with an input field for explanation
- A visual notice appears next to the file which shows that this file is checked-out, with the username/timestamp of the file check-out
- The user is subscribed to the file automatically (user is alerted any future changes are made to that file, including uploads)
View for the file for people (does not include the reserver). Note that if you expand the +,
you will see the original file, granting access to all original features.
View for the person who has reserved the file. They have two actions; "Unreserve" and "Cancel reservation"
The "Unreserve" button's terminology will change before final.
Users want to be notified of a file check-in
- User sees a file checked-out and wants to be notified for when it gets checked back in.
- User clicks "Notify me of unreservation"
- When a file gets unreserved (either through cancellation or new file upload), an email is sent to the user
Users want to cancel notifications for file check-in
- User sees a checked-out file they have subscribed to notifications for
- User clicks "Cancel my notification" to cancel the subscription
User lifts reservation on file with changes
- User complete changes to the binary file, and uploads the file back to the page
- If the filename matches against the checked-out file, then the file is considered checked-in and notifications for that file are now removed for that user
User (or administrators) lifts reservation on file without changes
- Original reserver (or administrator) clicks "Cancel reservation" button to remove the reservation
- If the person who lifted the reservation was not the original reserver, then a message is sent to the reserver indicating the reservation has been lifted.
User lifts reservation on file by submitting any file
- User clicks the "Unreserve" button, which launches the attach file dialog with one row for a file
- The uploaded file will set with the filename for the new head revision
- This unreserves the file and unsubscribes to future file changes
User wants to download a reserved file
- If a file is reserved, users can click the expand icon to expose the file as it normally displays
User overwrites a reserved file
- When a file with the same name as the checked-out file is uploaded, the operation succeeds, but a visual UI error message is thrown, indicating to the user that they are overwriting a file that was checked-out, and that their changes will most likely be overwritten in the near future
- A notification is sent to the original user who has checked-out a file letting them know of the reserved file
- A warning message will also appear underneath the reservation message notifying the reserver that somebody uploaded a file after the reservation
- The reservation still remains attached to the last reserved user
Non-goals
- This feature does not do actual technical file locking ("hard" locks vs. "soft" locks)
- This feature will not work correctly with the non-web UI in its first iteration (Desktop Suite)
- We will utilize file properties to ensure future forward compatibility with the Desktop Connector
Technical Specification
Resources: Guerric (UI), Arne (API), Roy (Lead)
Implications in Core & commercial:
- ADDED: File rename API feature
- ADDED: PUT file version with rename
- REMOVED: "Gallery" feature in front-end; we will push other DekiScript implementations
- REWRITE: File listing to include images and generated by UI plugin
- Ajax loaded revisions
- Rename files, attach new file version
UI requirements
- Integration with PHP hooks to overload file table view
- Integration with notifications to send the proper notifications; will require API resources for this
- Addition of dialogs to display confirmation screens
- Installation module?
API requirements
- A file should never be allowed to have two reservations. It should always respect the older reservation and throw an error.
- The API side will be created as a DekiExtension
- File lock info is primarily going to exist out of band from the MindTouch File features
- Data is stored by service locally for qiery purposes
- Reason is duplicated as a file property for easy reservation discovery (which implictly provides reserving user and date)
- The extension will be responsible for generating the notification emails and sending them via the Email Service
- The extension listens to file events on pub sub in order to determine check-in, overwrites, etc.
- also checks against MindTouch API periodically to avoid out-of-sync issues due to missed events
Extension Data Types
Reservation
<reservation href="..." >
<file id="..." href="..." revision="...">
<user.createdby id="..."/>
</file>
<user id="..." href="..." />
<date.reservation>...</date.reservation>
<reason>...</reason>
<subscriptions>
<user id="..." href="..." />
...
</subscriptions>
</reservation>
Extension Features
GET:reservations
Retrieve reservations in order of reservation date. Only a user with admin rights can query reservations for a user other than themselves.
Query Parameters
| Name | Type | Default | Description |
| user | string? | none | The user to filter reservations by. Can be user id or the string 'current' (optional) |
| limit | int? | 100 | Max reservations to return |
| offset | int? | 0 | How many reservations to skip |
Response
| Response | Response Body | Description |
| Ok (200) | application/xml | A reservation exists and the body is the Reservation document described above |
| Unauthorized (401) | text/html | Missing or bad Deki session |
| Forbidden (403) | text/html | Authenticated user is not authorized to reserve the file |
| Not Found (404) | text/html | There is no reservation in place for the file |
Response Body
<reservations>
<reservation>...</reservation>
...
</reservations>
GET:reservations/{fileid}
Retrieve the reservation for a file, if it exists.
Response
| Response | Response Body | Description |
| Ok (200) | application/xml | A reservation exists and the body is the Reservation document described above |
| Unauthorized (401) | text/html | Missing or bad Deki session |
| Forbidden (403) | text/html | Authenticated user is not authorized to reserve the file |
| Not Found (404) | text/html | There is no reservation in place for the file |
Response Body
The Reservation document from above.
PUT:reservations/{fileid}
Create or modify a reservation.
Query Parameters
| Name | Type | Default | Description |
| reason | string | none | Include the Subscription xml in the response document (optional) |
Request Body
The PUT can either be an XDoc or simply the query argument reason. In the case of the query argument usage, there either must be no existing reservation or the existing reservation must be owned by the authenticated user and the query body MUST be empty.
While the body can be the full reservation document, the only part considered is the reason, i.e. the following is the minimum document for the PUT:
<reservation> <reason>...</reason> </reservation>
Response
| Response | Response Body | Description |
| Ok (200) | application/xml | The reservation was stored |
| Unauthorized (401) | text/html | Missing or bad Deki session |
| Forbidden (403) | text/html | Authenticated user cannot modify the existing reservation |
DELETE:reservations/{file}
Cancel or check-in an existing reservation (also cancels all subscriptions). If the current version of the file is by the reserving user and is newer than the version at check-out, a delete triggers a check-out. Note: a check-out will also automatically happen via the file update event. Using delete after an upload exists so that the UI can make sure the reservation is no longer in place before reloading the file list.
Response
| Response | Response Body | Description |
| Ok (200) | application/xml | The reservation was deleted (although it might not have existed in the first place) |
| Unauthorized (401) | text/html | Missing or bad Deki session |
| Forbidden (403) | text/html | Authenticated user cannot cancel the existing reservation |
GET:reservations/{fileid}/subscriptions/currentuser
Retrieve the current user's subscription. Exists primarily as a quick way to check whether a particular user is subscribed to a reservation on file.
Response
| Response | Response Body | Description |
| Ok (200) | application/xml | A reservation for that user and file exists |
| Unauthorized (401) | text/html | Missing or bad Deki session |
| Forbidden (403) | text/html | Authenticated user is not authorized to view the reservation |
| Not Found (404) | text/html | There is either no reservation or the current user is not subscribed to the reservation |
Response Body
<user id="..." href="..."/>
PUT:reservations/{fileid}/subscriptions/currentuser
Subscribe the current user to a reservation
Query Parameters
None
Request Body
None
Response
| Response | Response Body | Description |
| Ok (200) | text/html | The subscription was stored |
| Unauthorized (401) | text/html | Missing or bad Deki session |
| Forbidden (403) | text/html | Authenticated user cannot subscribe to the reservation |
| Not Found (404) | text/html | No reservation for {fileid} exists, i.e. no subscription can be added |
DELETE:reservations/{fileid}/subscriptions/currentuser
Remove the current user from the subscription
Response
| Response | Response Body | Description |
| Ok (200) | text/html | The subscription was removed |
| Unauthorized (401) | text/html | Missing or bad Deki session |
| Forbidden (403) | text/html | Authenticated user cannot cannot unsubscribe from the reservation |
GET:subscriptions/{userid}
Retrieve reservations in order of reservation date. {userid} can be either the numeric user id or the string 'current'. Only a user with admin rights can query subscriptions for a user other than themselves.
Query Parameters
| Name | Type | Default | Description |
| limit | int? | 100 | Max reservations to return |
| offset | int? | 0 | How many reservations to skip |
Response
| Response | Response Body | Description |
| Ok (200) | application/xml | A reservation exists and the body is the Reservation document described above |
| Unauthorized (401) | text/html | Missing or bad Deki session |
| Forbidden (403) | text/html | Authenticated user is not authorized to reserve the file |
| Not Found (404) | text/html | There is no reservation in place for the file |
Response Body
<reservations>
<reservation>...</reservation>
...
</reservations>
- Tag page
- What links here
Files 6
| File | Version | Size | Modified | |
|---|---|---|---|---|
| ||||
| ||||
| ||||
| ||||
| ||||
| ||||
Copyright © 2011 MindTouch, Inc. Powered by
@arnec: If the change I suggested for check-in would require a fundamental change to the file attachment or versioning process, then I agree with you. If this can be implemented simply in the UI, and in a way that won't require extensive unwinding when the file versioning module is re-written, then I think it is worth it for ease of use and intuitiveness sake.
1) Should be possible for a user with certain privilege level (Admin?) to cancel a lock created by someone else. I can't tell if this is included here.
2) I am unclear how this would interact with the Webdav editing feature. Would that have to be disabled, or could it coexist peacefully somehow?
Looking at the screenshot you've added to this page, I realized that there is no way to determine what has changed in the new version of a file. If it is possible within the scope of the work you are doing, I would suggest that you add a field to capture "Notes" or "Summary of changes" to allow users to provide some information about the changes on check-in. Unlike a true DMS system, this should probably be an optional field in Mindtouch so that it is not restrictive.
This small change will make it easier to quickly identify a specific version of a file (e.g., "the version prior to when I accidentally corrupted the calculations in the spreadsheet". After all, this is one of the best use cases for implementing the check-in/out feature for attachments.
Re terminology, I'd shy away from "locking" because it's not actually locked. "Check in/out" makes sense to those who have used a DMS before, but when you think of it, it's not like a library either - the file hasn't gone anywhere, you can still access it. I can explain "reservation" more easily to users I think - it's like a reserved table in a restaurant, or a jacket on a seat in a movie theatre. Someone's telling you that they don't want you to sit there - but if you want to, you can do so anyway. (If it's the CEO's jacket on the chair, maybe think about sitting elsewhere, or contacting her before sitting down...)
@RoyK re admin cancelling locks: potential use case when a user has left the organisation. You could reset their password and log in as them to do it, I suppose. If they have many locks then a back-end option for the admin to "release all locks for user RoyK" may be good. No, we shouldn't expect that many users will have a lot of locks... but some will, even if it's not sensible. And if those locks can't be released by the admin then they'll stay there annoying other users with pop-up warnings forever, I presume?
/pedantic: On the screen shot, the second button should be "cancel check-out"