> Date: Wed, 6 Oct 2010 19:47:02 +0200
> From: [email protected]
> To: [email protected]
> Subject: Re: [authors] Base Guide
>
> 2010.10.04. 22:23 keltezéssel, Cecilia Cheung írta:
> >> Date: Mon, 4 Oct 2010 12:57:21 -0400
> >> From: [email protected]
> >> To: [email protected]
> >> Subject: Re: [authors] Base Guide
> >>
> >> Cecilia Cheung wrote:
> >>> An outline of restructured chapter 1 for the Base user guide is now
> >>> available in the feedback folder, please let me know your comments.
> >>> Cecilia
> >>>
> >> Looking through your proposed outline for restructuring chapter 1, I'm
> >> wondering if the outline for the entire Base Guide should be revised
> >> extensively as well as well (perhaps rewritten). The later chapters
> >> would flow better from what is introduced in Chapter 1 than they would
> >> as they are now written. Just one of my thoughts.
> >>
> >> Earlier, mention was made for whom we were writing the Base Guide.
> >> What do we think their expertise in using databases will be? If they
> >> have an database educational background, they will already know the
> >> technical terms which apply to databases. What about those who have not
> >> had a class in databases? How much of a problem will the technical terms
> >> to be introduced in Chapter 1 be to them?
> >>
> >> Here are the technical terms to which I refer: entities,
> >> attributes, secondary key, and database management system. Terms used
> >> within base include field name, field type, field properties,
> >> relationships (inner join, outer left join,outer right join, full outer
> >> join, and database engine. Another term use: RDMS (relational database
> >> management system).
> >> My concern is that introducing too many new terms too quickly
> >> might create some problems for those not familiar with technical terms.
> >> To understand what is written, the reader must understand at least 75%
> >> of the words. (So stated a college professor as she taught teachers how
> >> to make reading more understandable by their students). Perhaps my
> >> concerns will be addressed, and I am reading something into the outline
> >> more than is there.
> > My intention of including a section on database concepts is to help those
> > who have very little knowledge about databases. Hence, the coverage will
> > only be the bare essentials so that they can relate to fields, field types,
> > database types etc. when creating a database& table in Base.
> The proposal of Chapter 2, fit into the original outline Appendix II.
> http://www.oooauthors.org/english/userguide3/db3/outline
> > It also helps to visualise where/who they are in this process. I can
> > imagine that for those who just want to create a database for their musics
> > collection would probably use the Wizards, as there are predefined fields
> > to select. Hopefully those basic concepts will help them to understand why
> > those fields exist.
> For this we have documentation in OOo Getting Started guide Base Chapter:
> http://wiki.services.openoffice.org/wiki/Documentation/OOo3_User_Guides/Getting_Started/Getting_Started_with_Base
>
> I read Dan's today email and I agree with him, that this Guide main
> users not a database admins, ordinary users with some OOo background,
> and some basic knowledge.
Base provides templates for two categories, i.e. Business and Personal.
Therefore, the documentation of Base should cater for those occasional users
who decided to use Base to create a database for their personal use, for
example: a collection of plants. I see a user guide as a stand alone document
describing the software, and how to use its features on offer. A database
system is a complex subject, and Base is built with wide range of
functionalities and users in mind. It is very difficult to decoupling the need
for some terminology explanation if our aim of the guide is to help users
easily and quickly locating the information they need to use the software. For
those experienced users or have had some knowledge about database system, they
can skip the section on essential concepts. Therefore, the introduction section
will give clear suggestions on how to use the guide.
> I know that from my experience, which is less than Dan's I started
> around OOo 2.0.4 use OOo, from OOo 2.3 I use Base, that the good
> database design needs to work effectively, and for this needs some
> theory, but if we put into first part of guide and readers see it, may
> be they not read further. For this reason I suggest that your outline
> Chapter 2 fit into annex.
> I'm an aircraft+quality engineer with some IT+Access user knowledge, no
> formally educated as you, I read several SQL books, and tried examples,
> and discovered OOo Base limits by experience, and some Base QA work in
> last year.
I think you have done really well in achieving what you have done for Base.
What is so great about OOo is that it is a community of people with diverse
background and knowledge working together for the common good of a product to
be use free of charge. I believe we are all interested in learning, and to
enrich each other, so let us go forward with the full knowledge that we can
support each other no matter where we are in the world or in life.
>
> My personal view is that the present outline fit for the guide users we
> aimed with it.
> Regards,
> Zoltan
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
