• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

Question to Lone Wolf about Import/Export file details

I am reluctant to link to it as it is in the beta forum, and not everyone would have access to it.

Users with beta access can find the thread (2 pages) under the title "Import of own data".
 
@kbs666: We can't. The beta testers live in two worlds and they're trying to share some of their other world knowledge here. Given the volume of posts I'm sure it's hard for them to remember what has been discussed in public. Especially when public and beta are having the same conversations.

The take-away for me is the beta team is actively thinking about this, testing this, and talking to the devs about this. Unlike us, they have a much more direct link to them. So it's a win-win for us.
 
It is especially confusing when the conversations are in both places, because the beta members have agreed to NDAs. In general, if the information has been announced in public, the NDA no longer applies ... but remembering which details are and are not public makes me conservative on what I say in the public forums.
 
It is especially confusing when the conversations are in both places, because the beta members have agreed to NDAs. In general, if the information has been announced in public, the NDA no longer applies ... but remembering which details are and are not public makes me conservative on what I say in the public forums.
Yep. Pretty much easier for me to say almost nothing on the main forums anymore. :)

Worse for me is how much NDA stuff I have for Hero Lab I am not suppose to say. :p
 
Knowing the conversations are underway is comforting. When betas are managed well they are very effective. A big thank you to the beta folks that are watching the public forums and bringing our concerns to the devs so they don't have to spend their time poring over every post.
 
Hopefully Rob will answer the question if it is asked directly,

Can RW import an XML file if it was not created by RW but is in the correct form. We can surely provide some form of UUID's and signatures but they would not be what RW itself expects, obviously, unless LWD reveals how those are created.

Yes, you can create an XML file in the correct format, which it should be possible to import into RealmWorks.

If you look at the XML output of my script then the UUID and signatures are not required on the topics which you are importing. (They are required on the elements in the structure definitions, but not in the actual topics.)

(If you want to be able to import data more than once, then you will need to be able to put some form of unique id in for each topic; and use that same unique id when you re-import it. I assume this is achieved using the UUID attribute on the topic elements.)
 
What is to stop you from creating a bogus realm with a bunch of blank entries, exporting them and comandeeeing the uuids for import?

This is possible. You would have to create a lot of uuids to cater for adding more topics later on subsequent exports. You could also assign pseudo-random uuids using a microsoft library from within powershell.

The problem in making a general purpose script is to make the effort the least number of steps possible for a general user. So any use of UUIDs should ideally not be known by the average user of the import script.
 
I am reluctant to link to it as it is in the beta forum, and not everyone would have access to it.

Users with beta access can find the thread (2 pages) under the title "Import of own data".

I was answering Zaphod's original post in this thread :-)
 
Various notes regarding the import/export mechanism and assorted questions asked above...

1. We have a formal XSD for the import/export file structure. One of the tasks on our todo list is to properly annotate it with explanations of everything. My guess is that it will be another week or two before that gets done, though.

2. Anything to do with the XML structure can be freely discussed here. Even if it's something we shared privately with the Beta team prior to release. The XML structure is intended to be a public format. We just haven't gotten it documented yet. :)

3. When we designed the import/export mechanism, we never considered the use case of someone repeatedly importing material from another source. We figured that content would come in and then potentially cycle back and forth with another tool, but we never envisioned continually importing from the same source - which is what @Farling is doing with Obsidian Portal. Consequently, there is nothing in place right now to handle the one-time generation of uuids that can subsequently be re-used. This is something we'll need to consider and solve in the future.

4. The "original_uuid" and "signature" attributes are something that should NOT be used when importing from another source. They have a very specific use in conjunction with import and are for internal use only - at least, until we get a chance to re-think #3.

5. The uuids used by RW are of the same general format as standard guids, but their composition is unique to RW. If you generate your own uuids, you absolutely run a risk of rendering all your data unusable due to the uuids being invalid.

6. Use of uuids not explicitly generated by RW will present the opportunity for errors, and the validity of uuids is critical to the proper operation of RW. Consequently, we won't be sharing how the uuids are generated. The only real possibility here (that we've thought of so far) is to enable RW or some other tool to generate a block of uuids that can subsequently be used.

7. Generating uuids from one realm and then using them for other content in a different realm is going to create a vast sea of problems that even risks contaminating other realms in the database. Please don't do that, as the results could be disastrous.

I have a suggestion for how you might work around things on a temporary basis that I'll post in the Beta forums. It's something that would maybe work now, but it will NOT work in the future, so it's not something suitable for posting here. A proper long-term solution is needed for #3.

Hope this helps!
 
Back
Top