MobileRead Forums - View Single Post

StillReading · 09-16-2014, 08:24 AM

Thanks for all that information! All of these solutions aren't feasible for me though, unfortunately.

Let me explain, maybe the info is of interest to the development community. Background: I'm an IT professional, with a little experience in coding/scripting. I never coded anything in Python, though.

Suggested solutions:

1) code a metadata plugin: not feasible for me at all. I had a look at the code of other metadata plugins, and it seems it's not enough to adapt existing code. I'd have to build the plugin from the ground up, and learn Python (and other stuff, like how to properly use RegEx) while doing so.

2) URL/URI identifier: AFAIK, only one such identifier can be used for a book. This isn't a problem per se, but I've already "used up" that one URL/URI for many books for a different purpose. Besides, The "raw data" I'd need are the numerical IDs alone, the rest of the URL would be superflous data.

I currently have no idea for a solution/workaround. I'll probably go with the custom database field, though this makes editing data a PITA, and is probably not optimal in terms of performance. In a perfect world, adding custom IDs would be exposed via the GUI, allowing stupid users like me to simply add a new identifier (like amazon_de etc.), an URL portion, and then just add the new identifier and id number to the "ID" field.

09-16-2014, 08:24 AM	#4
StillReading Enthusiast Posts: 30 Karma: 10 Join Date: Sep 2014 Device: none	Thanks for all that information! All of these solutions aren't feasible for me though, unfortunately. Let me explain, maybe the info is of interest to the development community. Background: I'm an IT professional, with a little experience in coding/scripting. I never coded anything in Python, though. Suggested solutions: 1) code a metadata plugin: not feasible for me at all. I had a look at the code of other metadata plugins, and it seems it's not enough to adapt existing code. I'd have to build the plugin from the ground up, and learn Python (and other stuff, like how to properly use RegEx) while doing so. 2) URL/URI identifier: AFAIK, only one such identifier can be used for a book. This isn't a problem per se, but I've already "used up" that one URL/URI for many books for a different purpose. Besides, The "raw data" I'd need are the numerical IDs alone, the rest of the URL would be superflous data. I currently have no idea for a solution/workaround. I'll probably go with the custom database field, though this makes editing data a PITA, and is probably not optimal in terms of performance. In a perfect world, adding custom IDs would be exposed via the GUI, allowing stupid users like me to simply add a new identifier (like amazon_de etc.), an URL portion, and then just add the new identifier and id number to the "ID" field.