Realm Works Importing/Exporting advice

[rwap]

Hi

I've got three realms, one of which is a copy of another. I've done some work on the 'child' realm which I tried to export and import into the 'parent' realm. The import didn't work at first, the .xml version needed changing in the file which I did and then it worked.

It seems that the imported realm caused chaos because of tags.

What is the best way to clean the data before import?

[JustinThomason]

My understanding is best practice is to only ever make changes to your "parent" realm and then export from that to import the changes into your "child" realm. Trying to go the other direction causes issues.

That said, I've only done minimal work with the whole export/import function.

[Ualaa]

I've not used this, but it seemed really useful so I saved it:




I currently have 4 realm templates.

Blank - Completely empty. ALL default categories/tags are disabled or deleted.
Structure - This contains all the categories/tags all my realms use. I don't use any of the defaults.
Gamesystem - This contains all the game specific categories/tags my realms use, PLUS the import from Structure.
World - This contains all the world lore etc. that all my realms use, PLUS the import from Structure.

When I want to create a new realm, I first COPY the blank realm.
Next I open that realm, and import a STRUCTURE-ONLY export from the Structure realm.
Then I import a FULL export from the World and/or PF2 realms.

ALL imports require using advanced options and checking the boxes for OVERWRITE conflicts.

ALL exports have "preserve ownership" checked. This is super important.

If you try to create any topics in the totally blank realm RW WILL CRASH. Make sure you have some sort of category for every possible section.

If I make a change to any of the template realms and re-export, all my changes easily import to my active realm.

Example:
Partway through creating a realm, I realized I needed another snippet in a category. I saved and synced my current realm, switch to the Structure realm, and made my change. Exported preserving ownership, imported to my current realm overwriting conflicts, and the category now has the additional snippet. Any previously created topics require a resync or manual add to get the new snippet, but all newly created topics afterwards have it.

It took quite a bit of trial and error to get this all to work, but it was well worth the effort.

[Syrkres]

When doing a custom export, do you have to "TAG" every snipet or just the parent element?

[Farling]

Originally Posted by Syrkres

When doing a custom export, do you have to "TAG" every snipet or just the parent element?

You tag which topics/articles you want exported.

You don't need to mark each snippet in every single topic/article.

[Syrkres]

Thanks Farling!

[kbs666]

Originally Posted by Syrkres

When doing a custom export, do you have to "TAG" every snipet or just the parent element?

There is a bulk tagging feature to do this in one step. Create a view and add all the stuff you want to export and then bulk tag them.

[Syrkres]

Ok, in manage => tags I do not see an "Export" tag, yet when I go to Tag (on right had side of an object, and Click "Assign Tags to Topic" I see an "Export" tag with two sub-tags(which I think I created but don't remember).

Do I create "export" tags only when exporting or do I create them under Manage=>TAgs and then assign them?

I'm looking to create a Tag for "Custom Export" which I can assign when I want to export a few elements/objects?

[kbs666]

You cannot create the tags except through the export process.

Start an export, choose partial export, create the tag, exit the export dialog, create a view and assign the topics you want to export. Use bulk tagging to assign the tag to all the topics in the view. Go back to the export dialog and go through the partial export process.