Sa isa o aking pinakaunang post sa blog, Ako inilarawan sa pangkalahatang proseso namin sinundan upang i-migrate ang isang customer mula sa SPS 2003 to MOSS. A reader left a comment asking for more detail and here it is.
Para sa migration na proyekto, nagkaroon kami upang makahanap ng isang mahusay na paraan upang ilipat ang isang pulutong ng SPS 2003 documents over to MOSS. The initial load was easy enough. Create a new target document library in MOSS and use windows explorer to move the documents.
Ito ang bagong library dokumento:
Open up two windows explorers. Point the first at SPS 2003 and the second at the new document library in MOSS. The following screen shot shows this. Note that the top browser is actually pointing at my c:\Temp biyahe, ngunit maaari mong isipin na ito na tumuturo sa isang SPS 2003 dokumento library:
Matapos na i-drag at drop operasyon, ang aking target na ganito ang hitsura:
Now it’s time to deal with the metadata. Assume we have just one column of metadata for these documents named "location." We can see from the above "all documents" view that the location is blank. It’s easy enough to use a data sheet view to enter the location, or even go into each document’s properties one by one to add a location. Let’s assume that there is no practical way to assign the location column a value automatically and that end users must do this by hand. At saka, sabihin ipinapalagay may mga daan-daan ng mga dokumento (siguro libo-libo) and that it will take many many days to update the metadata. As we all know, no one is going to sit down and work for four of five days straight updating meta data for documents. Sa halip, they will break that out over a period of weeks or possibly longer. To facilitate this process, we can create an "untagged data" tingnan tulad ng ipinapakita:
Ngayon, kapag may nag-down na nakapatong sa kanilang paggastos inilalaan oras araw-araw o dalawa na i-tag migrate na dokumento, they can use the "untagged documents" tingnan upang ituon ang kanilang mga pagsisikap:
Tulad ng mga gumagamit ng mga dokumento tag, sila drop off sa listahang ito.
This notion of an untagged data view can also help with a class of data validation problem people inquire about on the forums. Sa labas ng kahon sa, there’s no way to prevent a user from uploading a document to MOSS and then not enter meta data. We can specify that a particular site column is mandatory and the user won’t be allowed to push the save button. Gayunman, kung ang pag-upload ng user at pagkatapos ay isinasara ang browser (o gumagamit ng mga bintana explorer upang i-upload ang dokumento), hindi kami maaaring pilitin sa gumagamit na magpasok ng meta data (muli, sa labas ng kahon).
This approach can be used to help with that situation. We can use a "poorly tagged data" view to easily identify these documents and correct them. Couple this with a KPI and you have good visibility to the data with drill-down to manage these exceptional circumstances.
</dulo>
