I’ll give it a look. I’m still in the early stages of the project, so it’ll be a bit before I get to the point where I work on the database side of things.

Your order is correct!

With the help of the other comment suggesting to measure the voltage of VCC, I was able to verify all the pins were working.

I have the pin order now!

I (very carefully) tested the pins for a brief moment to verify it all was working.

First I verified the voltage of vcc as 3.5v. Red to that and black to ground worked with no problems.

I figured the blue was probably in it’s correct place so I tried it and got video.

Quick test with green have me LED power.

The male part of the plug is borked, so I’ll just solder the wires on. Might even fashion up my own plug if I’m feeling fancy. I’m sure I got some spare connectors lying around somewhere.

Sadly didn’t find any. Even looked at other camera scores in the similar budget range with the hopes that the camera part is reused on other devices. No luck. Not many teardowns of scope cameras.

It’s a bit old and on the budget side. I’ll keep that in mind as a last resort.

The label is for the through holes, but I did confirm the corresponding pins for the plug with my multimeter.

I don’t believe the pins in the cable are in the right places. I guess they were reinserted wrong when it was first opened up. Pin 2 is definitely a dead pin. I confirmed the ground pin to the battery connection.

After reading some of the other comments, I’m definitely going to separate the systems. I’ll use something like json or yaml as the output for the raw scraped data, and some sort of database for the final program.

That’s an interesting read. I’ll definitely give json a try too.

Glad I could brighten up your day!

That’s good to know.

WhAt’S a CoMpUtEr?

Gonna be honest, I’ll need to research a bit more what validating against a schema is, but I get the general idea, and I like it.

For initial testing and prototypes, I probably won’t worry about validation, but once I get to the point of refining the system, validation like that would be a good idea.

One concern I’m seeing from other comments is that I may have more data than SQLite is ideal for. I have thousands of stories (My estimate is between 10 and 40 thousand), and many of the stories can be several pages long.

Gotcha. I think I’m aiming for something that runs off a single program. I want to be able to start it up whenever or even transfer it to a drive and use it on something like my laptop. Your idea sounds like it may work, but I’ll have to give it a deeper look.

I’m not entirely sure yet, but probably yes to both. The story text will likely stay unchanged, but I’ll likely experiment with various ways to analyze the stories.

The main idea I want to try is assigning stories “likely tags” based on the frequency of keywords. So castle and sword could indicate fantasy while robot and ship could indicate sci-fi. There are a lot of stories missing tags, so something like this would be helpful.

What’s your reasoning for that?

At this point, I think I’ll only use yaml as the scraper output and then create a database tool to convert that into whatever data format I end up using.

A few keywords in there I’ll have to look up, but I get the majority of it.

Yeah, I’m not too sure yet how complex the tags will be in the end. They are basically genres at the start, but I may make them more complex as I go.

After reading some of the other comments, I doubt I’ll use yaml as the main storage method. I do like the idea of using yaml for the scraper output though. Would give me a nice way to organize the data elements for each story in a way that can be easily read when needed.

Is this something that can be run locally without a server? I’m aiming for something as simple as opening the notes app on your phone and selecting a story.

That’s a good idea! Would yaml be alright for this too? I like the readability and Python styled syntax compared to json.