Maybe there was a typo. Because database construction has NOTHING to do with data entry. Maybe you might be entering information in the database, but I doubt you would be doing something else.
Database construction is building, and maintaining databases.
I am not sure what the details of the job are, but I think you should ask, for more information.
Please read below.
Web Site Development Database Construction
A good database is designed for a specific use and is constructed with the possibility of growth. We explained previously the functions of databases. Like web sites, "one size fits all" only ensures that your database may not have the flexibility you need. Your database may fail to collect the information you want and need for your business; or it may fail to provide your customers all the information they need to made a purchasing decision.
It is imperative that the developer designing your database understand the information you want to present and the different ways you may wish to present it (alphabetical order, by date, etc.).
For example, in a catalog you probably want to show the products both by name and perhaps in categories or by function. So when a user searches in pots and pans they find what they are looking for; but searching under kitchen items will also achieve listing pots and pans.
Of course if your database is going to collect information from customers, your developer will need to know what information you want collected and how that data will be displayed.
The database developer then must plan out the tables in the database so that all the information about an item or transaction can come together if necessary.
The owner of a database may wish to find out which customers not only purchased pots and pans but also purchased recipe books. Or they may want know which of their customers are located in New York City.
The output of a database depends on how well it was constructed and the building of relationships between one piece of data and another.
Careful planning and complete discussions with your web developer are very important to ensuring that your database meets your business needs, now and in the future. Therefore it is important not only to consider immediate needs but possible future uses of the data you collect.
Choose Your Database Developer Carefully
It is also important that you choose a web developer who really understands the importance of building a well constructed database.
Database Protection (Security)
Databases should be protected from corruption and from prying eyes. Your database may contain information needed by you but not to be shared with others. When you collect personal information, it is important to treat that information with care and security so that it is not available to prying eyes. Passwords are not sufficient for data protection.
Databases should be located "above the root", or in other words in a place on the server where web site uses are not allowed.
After Database Construction
Once your database has been built, data must be entered in the database. If your web site is an e-Commerce web site, you will load the product catalog, item by item, listing price, description, options (such as size, color, style). Each item will be given a product number so it can be easily identified. Often product numbers begin with letters to help identify the product by its number.
Normally the owner of the web site is responsible for loading the products and related information. Your developer will have loaded only some test products to ensure everything is working.
Other tables that may need information loaded are those containing administrative log-in names and passwords, shipping information, countries you will accept purchases from, and taxes and other charges.
It is the owner's (not the developer's) responsibility to determine if the web site must collect and remit state sales taxes, the European VAT tax and the required rates. A good accountant or lawyer will be able to help you with this determination.