"Time machine" for Document libraries

Kasper Bo Larsen
  • "Time machine" for Document libraries Kasper Bo Larsen

    Last week I got an interesting request from a customer: They would like to be able to see what a document library looked like at a given date. As far as I know this will require that the library 1) uses versioning, and 2) no limit to the number of versions

    A brute force approach would be to iterate each item in the SPDocumentLibrary and check the created date of the SPListItemVersion but that is far from an elegant solution.

    Is there a better way to identify the documents that existed at that date and return the current version at that date?

  • You could use the Lists Web Service to get at the versions using a Data View Web Part. Regardless, it'll be a bit of a logic challenge, as you allude to. I'm interested in what the use case sounds like on this one. Easy to ask for, perhaps hard to develop, but to what actual use?

    M.

  • Interesting request. If we continue the Time Machine analogy, do they just want to be able to 'see' what documents where there at that point in time or be able to open a document from that moment in time (would require lots of BLOB duplications)?

    You could attach a Workflow to the Library that every time a CRUD event fires, it writes the metadata to a history tracking List so they could see what items where there at that moment with anything you were tracking. Pretty quick and easy way to do this, as I had to do it once for a customer.

Tags
document versioning
Related questions and answers
  • We have a wss 3.0 site that has a document library based on a custom list definition. We would like to block users that have contributor rights from deleting documents, what is the best way of doing this?

  • I have a document library using a document set content type. I can create a new document set through the UI and it works perfectly. I'm now trying to create a document set in this library... for the set looks like a folder instead of the document set icon clicking on the document set doesn't show the document set home page, it just behaves like a normal document library running CAML queries shows that both internal fields HTML File Type and ProgId should be SharePoint.DocumentSet but instead they are blank changing a field value on the document set folder doesn't propogate to its contents

  • I have an InfoPath form embedded in a MOSS 2007 page. The form is for requesting approval for a project. The submit button submits the form data to a form library. That triggers a workflow to get approval for the request. So far, my workflow uses the "Collect Data From User" action and the "Send and email" action. I configured data collection option so that there are two inputs: two radio buttons for approve/reject and a comment field. I built the email body and subject using dynamic strings and variables from the form data. I would like this approval process to be simple for the person

  • What do you think of using email-enabled document libraries in SP2007? Is it reliable? secure? or too complicated to get it to work correctly? Also would it accept emails from "anyone" sending to that address? What about other fields the document library may have (like for example adding a single line of text field to hold a classification field for example).

  • A common issue with my customers is that they define a number of content types that should be available on a document library. That library is part of a custom site template and pretty soon we'll have 200 sites using that template. Now the customer realize that they need two new content types on that library. Oh, and they will need those content types on the existing sites as well. I might have misunderstod something about content types or just misconfigured the library, but so far the only way I have been able to add those new content types on existing sites have been through a powershell

  • Sorry if I'm getting the terminology wrong, I'm very new to sharepoint. Basically, a site I'm working on uses sharepoint for some versioning stuff in the background. I would like to be able to take the "schema" from production and have developers able to use it locally for their own development and testing. I don't need all the files contained within. I'm just looking for a way to easily copy the site structure and document library structure to another machine. Is that possible/easily doable? Thanks in advance.

  • Another question about the Very Large List I referenced in this question: http://sharepoint.stackexchange.comquestions/445/deleting-old-versions-in-a-document-library This Document Library has over... is specified in the item's metadata. All of the documents currently live in the root of the Document Library. What we'd like to do is move the documents into folders by project to both improve.... No combination of setting things like ReadOnly="False" on the column, etc. seems to work. This is one capability that I would expect to be part of the Copy Web Service, as it's exposed in the UI

  • When opening a document from a documentlibrary in Word/Excel/Outlook the FileOpen Dialog shows all the files in the document library. I have a lot of documents in there, with metedata in columns. How do i show those extra columns (in the fileopen/save dialogs), and how do i enable filtering of those columns? Just finding my file based on only the filename is hard, using the metadata would be a great improvement.

  • The value of a column is the name of the library in which the document is being inserted. Users are objecting to supplying a value when the value is already known. Seems to me there are two responses to this: remove the column (and rely upon the document library name) or automatically choose the library name from the dropdown of library names. If the latter, how might that be done (without code)?

Data information