Re: Database Creation
Hi Julia,
I apologize in advance for the very long-winded post. I know no one is going to read it all. What Darlene said is so true. Go by that. And as others have said - it depends a lot on what the client needs.
To add a bit more on the terminology - there are two main entities - 1) the data, and 2) the database. The database is the "container" that holds the data. So there are different types of services you might provide:
1. A "user" uses a pre-built database to input data and maybe run reports. As a service, this might be called data maintenance or data updating - I'm not sure what people are calling it now - but I wouldn't offer it as "database" maintenance (see #4)
2. You could use a database as a tool in your own work (for your own use - you are both the creator and user). Your contract with the client is then just the input and the output. The client would advise what data they want collected (the input) and what information they want from it (the output - reports, charts, spreadsheets, whatever). You don't give them the database afterwards. They will probably want the data, but I would supply the tables only (or a spreadsheet). If you do give them the full database you used, I would add a disclaimer of some sort - or you may be expected to do #4 as part of what they've already paid you. If they wanted a database to use for themselves, they should be starting at #3.
3. "Database development" for others (requires more formal analysis, design, developing, testing, documenting, installing, training, etc) - it has to be more professional and user-friendly than what you might build for your own use. And it may involve investment in various database software.
- could be creating a single-user database for one other "user" to use (easier)
- could be creating a multi-user database that several other "users" use (harder)
4. "Database maintenance" generally refers to ongoing support for something you developed in #3 - fixing bugs, upgrading, enhancing, etc (i.e., it doesn't mean inputting data).
5. And heaven knows what might be involved in developing online databases... can't comment on that.
If you have Access in (Microsoft Office) you can learn the basics from books and playing around with it. It can, though, get complicated when you move from "simple" tables to "relational" tables. My personal recommendation is to take courses because I think it's important to get a solid foundation on how a database works.
My disclaimer: I worked in database development for quite a long time, but in a more corporate environment - not as a virtual assistant. So my comments are coming from that perspective. The VAs who do this kind of work might have a different perspective - and maybe the terminology that I'm used to is different out there in the real VA world - maybe more relaxed. And maybe they have more options than what I have above. And MAYBE I'm just right out to lunch.
Actually, I'd like to know what they have to say about #2 - what they would advertise it as - whether clients want this service or not. That's what I'd like to offer.
Ok, I'm done.
Deb
|