SharePoint Migration Tip: Erabili “untagged datuak” Migrazioak Incremental Views

Bat edo nire Oso lehenengo blog-mezu, SPS bezero migratzeko jarraitu genuen prozesu orokorra deskribatu dut 2003 to MOSS. A reader left a comment asking for more detail and here it is.

Migrazio-proiektu, SPS asko mugitzeko modu ona aurkitu behar izan dugu 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.

Dokumentu berri honek liburutegia da:

image

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:\aldi baterako unitatean, baina SPS bat seinalatuz imajinatu dezakezu 2003 Dokumentu liburutegia:

image

Arrastatu eta jaregin eragiketa, eta ondoren, nire Helburu itxura:

image

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. Gainera, Demagun ez dira ehunka dokumentuen (agian milaka) 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. Horren ordez, they will break that out over a period of weeks or possibly longer. To facilitate this process, we can create an "untagged data" ikusteko gisa agertzen dira:

image

Orain, norbaitek eseri behera bere esleitu eguneroko ordu bat edo bi pasatzeko migratu dokumentuak etiketatu, they can use the "untagged documents" ikusteko beren ahalegina bideratzen:

image

Erabiltzaile tag dokumentuak, utzi dute zerrenda honetan.

This notion of an untagged data view can also help with a class of data validation problem people inquire about on the forums. Kutxa Out, 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. Hala eta guztiz ere, erabiltzailearen fitxategiak eta, ondoren, nabigatzailea ixten bada (edo Windows Explorer erabiltzen dokumentua igo), ezin dugu behartu erabiltzaileari meta datuak sartu (berriro, koadroan out).

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.

</amaiera>

Nire blog Harpidetu.

Technorati Tags:

Utzi iruzkin bat

Zure e-posta helbidea ez da argitaratuko. Beharrezko eremuak markatu dira *