Brad Covey
2014-04-10 14:44:03 UTC
Hi Guys,
I'm uploading large files to GBrowse manually as custom tracks. I've
written scripts to create the sqlite database for the upload, the proper
folder structure under "userdata", and the entry in the users.sqlite
database.
The directory structure that is created looks like this:
userdata/
datasource_name/
user_uploadsid/
feature_name/
index.SQLite
STATUS
feature_name.conf
SOURCES/
feature_name
The upload seems to work fine and the new track appears under "Custom
Tracks" as shown in the following screenshot:
[image: Inline image 1]
here "might-have-fixed-the-featurefile" is the new upload.
But the upload is not shown under "Select Tracks":
[image: Inline image 2]
I've done a bit of troubleshooting to try to figure out why this is
happening. I've narrowed the problem down to the entry in the "uploads"
table of the "users.sqlite" database.
These are the current entries in the database:
"2","private","trying-again",
"","yoxphwmgxhjlzf3ngjk3ew5xbuwnoytl","Toceanica2","2014-04-08
16:24:11","2014-04-08
16:24:11","","trying-again", "0"
"2","private","might-have-fixed-the-featurefile","","6c0yilb5r2yirwffht32ixg1tusdsjpk",
"Toceanica2","2014-04-10 10:42:03","2014-04-10
10:42:03","","might-have-fixed-the-featurefile","0"
I included the "trying-again" entry as a working example for reference.
note: the trackid is 32 characters long for both
As far as I can tell there is no difference between the two entries, but if
I point the working "trying-again" entry at the non-working
"might-have-fixed-the-featurefile" path like so:
"2","private","might-have-fixed-the-featurefile","","yoxphwmgxhjlzf3ngjk3ew5xbuwnoytl","Toceanica2","2014-04-08
16:24:11","2014-04-08 16:24:11","","trying-again showing
might-have-fixed-the-featurefile","0"
"2","private","might-have-fixed-the-featurefile","","6c0yilb5r2yirwffht32ixg1tusdsjpk",
"Toceanica2","2014-04-10 10:42:03","2014-04-10
10:42:03","","might-have-fixed-the-featurefile",
"0"
My initially non-working track is displayed properly:
[image: Inline image 3]
Which tells me that the folder structure, sqlite sqlite database, and
configuration for my new custom track are being created properly but there
is some problem with the entry in the "uploads" table of the users.sqlite
database preventing the track from being displayed properly.
Does anyone have any idea what may be wrong with the "uploads" entries that
my script is creating?
Thanks,
Brad
I'm uploading large files to GBrowse manually as custom tracks. I've
written scripts to create the sqlite database for the upload, the proper
folder structure under "userdata", and the entry in the users.sqlite
database.
The directory structure that is created looks like this:
userdata/
datasource_name/
user_uploadsid/
feature_name/
index.SQLite
STATUS
feature_name.conf
SOURCES/
feature_name
The upload seems to work fine and the new track appears under "Custom
Tracks" as shown in the following screenshot:
[image: Inline image 1]
here "might-have-fixed-the-featurefile" is the new upload.
But the upload is not shown under "Select Tracks":
[image: Inline image 2]
I've done a bit of troubleshooting to try to figure out why this is
happening. I've narrowed the problem down to the entry in the "uploads"
table of the "users.sqlite" database.
These are the current entries in the database:
"2","private","trying-again",
"","yoxphwmgxhjlzf3ngjk3ew5xbuwnoytl","Toceanica2","2014-04-08
16:24:11","2014-04-08
16:24:11","","trying-again", "0"
"2","private","might-have-fixed-the-featurefile","","6c0yilb5r2yirwffht32ixg1tusdsjpk",
"Toceanica2","2014-04-10 10:42:03","2014-04-10
10:42:03","","might-have-fixed-the-featurefile","0"
I included the "trying-again" entry as a working example for reference.
note: the trackid is 32 characters long for both
As far as I can tell there is no difference between the two entries, but if
I point the working "trying-again" entry at the non-working
"might-have-fixed-the-featurefile" path like so:
"2","private","might-have-fixed-the-featurefile","","yoxphwmgxhjlzf3ngjk3ew5xbuwnoytl","Toceanica2","2014-04-08
16:24:11","2014-04-08 16:24:11","","trying-again showing
might-have-fixed-the-featurefile","0"
"2","private","might-have-fixed-the-featurefile","","6c0yilb5r2yirwffht32ixg1tusdsjpk",
"Toceanica2","2014-04-10 10:42:03","2014-04-10
10:42:03","","might-have-fixed-the-featurefile",
"0"
My initially non-working track is displayed properly:
[image: Inline image 3]
Which tells me that the folder structure, sqlite sqlite database, and
configuration for my new custom track are being created properly but there
is some problem with the entry in the "uploads" table of the users.sqlite
database preventing the track from being displayed properly.
Does anyone have any idea what may be wrong with the "uploads" entries that
my script is creating?
Thanks,
Brad