A A A
Avatar

Please consider registering
guest

sp_LogInOut Log In sp_Registration Register

Register | Lost password?
Advanced Search

— Forum Scope —




— Match —





— Forum Options —





Minimum search word length is 3 characters - maximum search word length is 84 characters

sp_Feed Topic RSS sp_TopicIcon
Operator log forms
Avatar
Veerle De Bock
Member
Members
December 12, 2014 - 9:52 am
Member Since: October 1, 2013
Forum Posts: 4
sp_UserOfflineSmall Offline

Hi everyone!

As the deadline for the operator log form is the end of January 2015, we need to proceed with this as quickly as possible...

According to Volodya, we should not try and convince station operators to switch to a new log, they should continue using what they already use.
We should however collect all available forms (even paper log forms) and store them in the database. For the digital forms, we should just read all
the forms (we probably need a program for this) and put the information together into one new general form (where some of the columns can remain
empty, depending on the information that is available from the individual log forms).

The date of logged information is something that is available in every form (either digital or paper) and this could be used as an indicator to check the data.
Even if the log forms only contain the date and some written log information, we know by using the date that something happened that day.

So If we collect every existing operator log form (both scanned paper versions or digital forms), we could then for instance create a general log table
in the database with the following information:
- station ID
- Brewer ID
- (begin and end) date for which the log form contains information
- name of the log file (+link to the file)
- email of the contact person

The link could be either to a digital file or to a scanned paper file.

I think it might be impossible to automatically flag the data based on the operator forms.
The only thing that might be done automatically is to check whether a certain date (for which you think the data is suspicious) is present in the log table.
If this is the case, I assume the best way to go forward is to contact the station operator and ask him to look at the data and flag them based on what he/she wrote in the operator log.
So next to the log table, there would then be a flag table with the following information:
- station ID
- Brewer ID
- date of logged information
- data flag
0: data is ok
1: data is suspicious
2: data to be removed

This is just a first proposal of how things could be done.
I look forward to your comments and suggestions!

Thanks!
Veerle

Avatar
Volodya
Member
Members
December 14, 2014 - 1:05 am
Member Since: October 1, 2013
Forum Posts: 4
sp_UserOfflineSmall Offline

Hey, I've edited the form somewhat and added a few comments there as well. Basically, I'm trying to push the same message as before: the form to be useful needs to be as much database-ready as possible. Thus: every row with data has to have a description; numbers preferably should have no units attached to them (if you have to have units it is best to have a separate column for that).

Hope this is helpful,

Volodya

Forum Timezone: Europe/London

Most Users Ever Online: 18

Currently Online:
1 Guest(s)

Currently Browsing this Page:
1 Guest(s)

Top Posters:

Member Stats:

Guest Posters: 0

Members: 87

Moderators: 0

Admins: 2

Forum Stats:

Groups: 1

Forums: 5

Topics: 1

Posts: 1

Newest Members:

OscarGliff, iioffimari, nusainclai, Curtisfam, BrianerM, Ludovicl, nburtonroman, Arnottzud, uermanuiaalex, rtzpatricbula

Administrators: brewermaster: 1, Webmaster: 0