SensorBase Blog

sensorbase now has table-level access control. you can find this option on your project settings page.

basically, you can think of access as a hierarchy. for example, if the user has project-level slog access then she can write to all project tables no matter what permissions you provide at the table-level. however, if you have *not* provided the user with project-level slog access and but have at the table-level, then she can slog only to your specified table.

ok, that explanation was kind of confusing. it’s probably easier if you just try it.

this involved quite a few changes in the code, so please let me know if you come across any bugs.

When you browse data, if you have are the project creator or have been granted “build” access, you now have the option to delete rows of data. Check the rows you want to delete, and then click the button on the bottom.

I’ve added documentation on how to slog data via an HTTP POST. The code snippets were adapted for beta (originating from alpha). I’m pretty sure I got everything, but of course, let me know if you have any troubles.

If you’ve created a sensorbase project, you can now add other sensorbase users to your project with one of three permission levels in project settings:

1. read — can retrieve data
2. read and slog — can read and slog data
3. read, slog, and build — can read, slog, and edit tables

If you’ve retrieved data from sensorbase, you’ve probably noticed that your previous preferences don’t carry over after you’ve done the initial retrieval. Well that’s fixed now, so you don’t have to re-enter the date every time you retrieve. There’s also a new button at the top of your list of fields that allows you to toggle all of the checkboxes.

While viewing a table, look to the navigation links on the right, and you’ll see a link to browse your data. If you created the project, you’ll be able to edit the rows as well.

As in Alpha, we’ve made table emptying available in the project view page. Since it involves deleting data, you’ll have to enter your email and password, and currently, you have to be the project’s creator to empty a table.

We seem to be having some memory issues that we didn’t have before. I’m not sure if it’s the new implementation or that there’s a whole lot more data coming in now. I have a feeling it’s the latter. We’re looking into some upgrades and possibly a new box, so please bear with us.

Until we get those upgrades, you can still retrieve all of your data. You’ll just have to split it up into like two pieces if you’re going to retrieve more than 100,000 rows of data. For tables with images, I you’ll have to start splitting at around 1,100 rows.

————

Update: We’ve centered in on what’s causing the problem. We’ll be getting some new hardware soon which hopefully gives us the fix.

With Python SOAP there was an authentication bug, but Gong has fixed it, and it’s good to go now. Enjoy!

We’ve added some documentation in the SensorBase help section on how to use the new SensorBase API. If you used the SensorBase Alpha API, you won’t have to change much. The functions are still the same. You just have to download the new SensorBase WSDL file, and that’s it.

If you’re retrieving media, there’s just one more thing. Instead of appending “http://sensorbase.org/alpha/” to the link that getData() gives you, append “http://sensorbase.org”. That’s it!

More documentation will be up very soon.