Looking for some advice before I resort to trial and error:
I have a migration project that requires me to move files from a default DNN repository to DMX. I am able successfully to migrate the files en masse by a combination of exporting the file names, copying and renaming (using VB Scripts) the files to remove the GUID that repository inserts into the file names and then using the DMX bulk import facility. So far so good.
But now the customer has sprung on me a requirement to migrate the associated file descriptions into the DMX remarks field. Here is what I have come up with as a pathway to doing this using SQL scripts and I hope you may be able to validate my ideas (or possibly suggest an easier method).
• From the grmRepositoryObjects table export the FileName and Description fields to a temporary table
• For each entry in this table truncate the file name to the first 7 characters (which is enough to uniquely ID the file)
• For each entry, identify the EntryID in the DMXEntries table where OriginalFileName starts with the above shortened FILENAME and add the EntryID to a column in the temp table
• For each entry in the temp table, insert into the DMX_LongTexts table with Locale="", ObjectID = the extracted EntryID, SubType=’REMARKS’, Text= the extracted Description field contents and TypeKey=’ENT’.
I believe I can do this using the Stored Proc DMX_AddLongText.
Any comments on the above would be gratefully accepted. My chief concern is how the system will handle the fact that the repository description is held using HTML coding – e.g. a typical entry will read ‘
This is the description
’ . Is this going to be OK or am I going to have to do some data manipulation to remove the HTML tags from the text strings before importing?
Thanks in Advance.
Graham