Jump to content

import script tooling


This topic is 6549 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Hello. I am working at getting a script working.

I am going to use this a s a simple log of the path to figure it out as I am new to filemaker pro.

If anybody feels like to help I will be glad to hear any help.

__________________________________________________________________________________________________

text looks like this ...

* xxxx xxxx x x x x xxx.xxx.xx.xx. xxx.x.xx.xx.xxx.xx.x..x xxx xxx x x x xxxx

xxx xxx xxx x xx xxxx xxx xxx x x x x x x x xxxx xxx xxx x x xxx x x x x xx

The real text is like this

* FROM CLIP NAME: OCEAN AND SHORE B-ROLL, JIM AND JIM ON BOAT CUTAWAYS

* KEY CLIP NAME: SHORTLY AFTER

111 6517 V K B 01:45:23:08 01:45:26:16 01:09:21:15 01:09:24:23

111 AX V K 000 00:00:11:17 00:00:14:25 01:09:21:15 01:09:24:23

* FROM CLIP NAME: OCEAN AND SHORE B-ROLL, JIM AND JIM ON BOAT CUTAWAYS

at * map then M blaaaaa

lots of numbers !

more numbers !

at * deni untill : then make into block til line break

if at each break after first line with * create sep blocks.

repeat

oooor!

Position count. = whatever result create number of slots copy text into slots repeat. Page 212

Link to comment
Share on other sites

Ridellin! laugh.gif

Umm, 6 fMPRO Aqua 10.3 osx .

Onwards !

Add break, create mass " tabs " at each space like "_" so it becomes " _______ " Out come is = to lots of mess still need algaritm to create voids and deny.

If nothing, then plan two. ??? A>I> control for Occtave vocal 3 point input output. COPY paste ....

Link to comment
Share on other sites

Just trying....

tripdragon said:

Hello. I am working at getting a script working.

I am going to use this a s a simple log of the path to figure it out as I am new to filemaker pro.

If anybody feels like to help I will be glad to hear any help.

__________________________________________________________________________________________________

text looks like this ...

* xxxx xxxx x x x x xxx.xxx.xx.xx. xxx.x.xx.xx.xxx.xx.x..x xxx xxx x x x xxxx

xxx xxx xxx x xx xxxx xxx xxx x x x x x x x xxxx xxx xxx x x xxx x x x x xx

The real text is like this

* FROM CLIP NAME: OCEAN AND SHORE B-ROLL, JIM AND JIM ON BOAT CUTAWAYS

* KEY CLIP NAME: SHORTLY AFTER

111 6517 V K B 01:45:23:08 01:45:26:16 01:09:21:15 01:09:24:23

111 AX V K 000 00:00:11:17 00:00:14:25 01:09:21:15 01:09:24:23

* FROM CLIP NAME: OCEAN AND SHORE B-ROLL, JIM AND JIM ON BOAT CUTAWAYS

at * map then M blaaaaa

lots of numbers !

more numbers !

at * deni untill ??? then make into block til line break

if at each break after first line with * create sep blocks.

repeat

Hmm... not yet, need a cigarette...be back later...

Link to comment
Share on other sites

OK, all jokes aside...

At a guess it looks like video clip meta-data, with name and time code stuff. The success of the parsing will depend upon how structured the string is. If the Clip Name is always on the first line following the colon (and everything is as easily predictable) then it'll be easy. If it changes every time then it'll be nigh on impossible to do anything without huge amounts of human intervention.

I would create an "import" file to do a heap of pre-processing before importing into the main database.

The import file would have one text field per record into which the data for each record is imported. (I assume that each clip info is delimited somehow so you can separate it into records, if not then it keeps getting harder.)

Create calculation fields in the import file that parse the text based on the structure of the string. For example, the first line is Clip Name, second line is Key Name, third is Start Code, Fourth is End Code, etc. (Scripts rather than calculated fields might be required if the parsing requires a significant amount of iterative processing, but the outcome will be equivalent.)

When it's been processed, import the parsed text fields into the main file.

As I said earlier, the success is totally dependent on the structure of the text string and how reliable the structure is.

Link to comment
Share on other sites

If you import the raw text into Excel first, you can quickly set field delimitation (column markers). Save the Excel file then import it into FM. Minimal parsing required. But if there is a reason you'd rather not run your data into and out of Excel before FM every time, then importing it as one big field into FM, then setting up a raft of calculation fields to pluck out the relevent bits is the way to go.

Steve Brown

Link to comment
Share on other sites

Sorry for not updateing, Been home geko. Back at work , Back to tests. Back to back.

One part I can not have it running through Excel, the file is HUGE ! I mean HUGE 15,000 data stacks HUGE, so it must be in FM all the way. Now a little Apple scripting could help a bit or A PHP html script thingy would also do, more updates to come around

Link to comment
Share on other sites

This topic is 6549 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.