Closed (fixed)
Project:
Table Manager
Version:
4.7.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Support request
Assigned:
Reporter:
Created:
17 Jul 2006 at 17:17 UTC
Updated:
26 Jul 2006 at 13:44 UTC
So far so great; I like this module.
I'm in the process of importing back logs - i.e transfering one huuge table into nearly a hundred individual ones, each separated by an identifiable datestamp. I can do one-by-one, but am wondering if 1) anyone can suggest something that could parse them all at once?
And 2) preserving the links. So far, I'm stepping through a spreadsheet and the cvs export drops all the links.
Any pointers?
Comments
Comment #1
pobster commentedHelloooo
I'm afraid anything like that will need to be custom written, although that's not all bad news ;o) If I deem your custom function to be helpful to the community then I'll write it myself, but if it's only really going to service your own needs then I'm afraid you'll either have to write it yourself, else ask for help on the forums...
I'm not sure I'm 100% clear on exactly everything... If you could post some examples then I'll have a much better idea of what it is you're trying to achieve. Tell me more about why the csv export drops the links as well? Have you tried exporting the spreadsheet to a different program and then creating csv from that? Let me know! :o)
Thanks
Pobster
Comment #2
brst t commentedThanks for the response.
I looked into writing a few wee scripts to parse my html tables, but really, they're a bit too messy from some 84 weeks of typing them out one by one.
A different program probably would have helped. Though, I still would have ended up having to import each table individually. Were I more familiar with the structure, I would have brought the data in through MySQL...
This is where a custom function could save many hours for many people using this module.
Importing a series of tables-
-Start new table at user defined character series eg. '%start%'
-Let the following line = table subtitle
-and the one after that = first row
Trish
Comment #3
brst t commentedAnd maybe permit user-defined separators? The numerous commas littered throughout were rather problematic, to say the least.
Comment #4
pobster commentedOkay as of 1.68, now have user defined separators.
Pobster
Comment #5
pobster commentedComment #6
pobster commentedJust to clarify with your other suggestions:
-Start new table at user defined character series eg. '%start%'
Sorry I'm not clever enough to do that...
-Let the following line = table subtitle
Meh, you can edit the table after it's created to add a description... I doubt many people even use the description anyway? I certainly don't...
Pobster