Lone Wolf Development Forums

Lone Wolf Development Forums (http://forums.wolflair.com/index.php)
-   Realm Works Feature Requests (http://forums.wolflair.com/forumdisplay.php?f=84)
-   -   Bulk Importer from file (http://forums.wolflair.com/showthread.php?t=50557)

RampagingHoardes September 2nd, 2014 02:40 PM

Bulk Importer from file
 
Any chance of a Bulk File Importer into RW?

It would be so helpful if we could read an entire pdf, word or comma delimited file into realm works as a topic(s) and then be able to tag the text and split it into further topics based on the tag we set. This would be a HUGE leap forward for the product.


A Bulk loader for Herolab would also be nice even if the data has be be massaged first to meet Hero Lab file specs.

Did a lot of this type stuff in the past so i am pretty sure this shouldn't be an issue other than time.

The amount of time saved by not having to do manual entry or to minimize manual entry would seize the gold for next year.

Fingers Crossed.

mirtos September 2nd, 2014 02:48 PM

+1, but i think it should be a CSV file.

RampagingHoardes September 2nd, 2014 03:11 PM

Quote:

Originally Posted by mirtos (Post 192039)
+1, but i think it should be a CSV file.

Honestly it should read any of what I listed to be the most helpful.

Many gaming books and modules are now pdf having the ability to import this directly is invaluable.

Cornelius September 3rd, 2014 01:43 AM

Although I would like this I think it will be trouble how to implement it properly.

For me the best option would be if I buy a product from a publisher in pdf I get a RW copy as well. ;)

chiefweasel September 3rd, 2014 03:49 AM

I had a long talk with a few of the developers at Gen Con during the meet and greet about this very thing. There are a few issues that need to be overcome, but they are looking at it. That being said it may be a while before anything is out for it.

Ladyofdragons September 3rd, 2014 05:38 AM

my mind is a tad boggled on how you would automate this.

Step 1 you would have to convert PDF to text. Sometimes this works well, other times not so much. Lots of editing may be required.

After you get it into text format, then you need to divide all that content up into topic chunks. That's not something that can be automated, you'd want to specifically design topics and heirarchy and content/topic type. Even if you wanted zero control over structure you'd have to break up the content somehow. Most publishers use different standards, and certainly different games do, so there's not really a sure way to determine how to automatically split content.

Lastly, you'd have to divide all those topics up into logical snippets, which also is not something that would be done remotely well if it was automated. Most you could do there is one big text snippet per topic, which you would then have to go through all the work splitting it up to be readable/useable anyway.

My feeling is you'd be much better off converting your PDF to text and doing logical human-led copy/paste. Or wait for the content to come out on the marketplace.

lfseeney September 19th, 2014 10:34 PM

There is a command for splitting a block of text into a new snippit, so getting the data in,
then using that to break it down would be much faster than the copy paste create new copy paste I would think.

Zaphod Beebledoc November 27th, 2014 04:04 PM

A big issue for me is the time I need to wait for RW to switch between topics, so any bulk importer, which I really, really, *really* would like, would ideally do the importing behind the scenes.

I've got a great deal of stuff I want to put in, and a lot of it is in Excel files.

With my limited database knowledge, I would think that comma separated value files, which Excel can create easily, would be the best way of doing it.

Would the best way to have a .csv detailing a topic and then it's snippets or a .csv that creates topics, then one that puts in aliases, followed by one that puts the birth dates in, and another for death dates, etc?

pickin_grinnin December 1st, 2014 01:09 AM

Quote:

Originally Posted by mirtos (Post 192039)
+1, but i think it should be a CSV file.

I agree. For me, .csv importability (and exportability) would be enough for me to actually start to put data into my copy of RW.

Dark Lord Galen December 1st, 2014 04:54 AM

I would agree a de-limited text type of import / export feature could be useful, BUT As LADY above points out, I can't wrap my mind around how LWD could do such efficiently...

Exporting is not as problematic since LWD can control how the data leaves RW.Once the ability to create PDfs or print comes into play this will help the sharing of data from an exporting perspective.

Importing is another matter all together.

Even Adobe (which is the defacto product) for PDFs cannot manage a perfect clean "copy" from PDF to say word *.doc file or an *.xls sheet of Excel. And all of these products have been around for YEARS.

I see ALOT of user clean up that would remove any "time savings" getting the data into the right snipits, tags, articles, etc... I then forecast numerous complaints from the community on wrecked databases, information in wrong places, etc and the community then wanting LWD to "fix it".:eek:

Currently cut and paste, (to me) seems the simplest most direct approach. I highlight what I want, and only what I want.. and put it where I want...

I just don't see this working... unless some copies of RW came with a leprechaun feature that magically does this?? IF so I need that patch!!! hehe seriously.... lets not put unrealistic expectations in front of ROB and Company for them to.... IMO... spend energy on that would glean little to no fruit.:cool:

Remember RW is a Database, so it is not only just getting the information in, it is also getting that information arranged properly. It isn't as simple as scanning a hardcopy document and creating a digital one.


All times are GMT -8. The time now is 09:14 AM.

Powered by vBulletin® - Copyright ©2000 - 2024, vBulletin Solutions, Inc.
wolflair.com copyright ©1998-2016 Lone Wolf Development, Inc. View our Privacy Policy here.