Stuff to figure out with NAWS and groups:
- We need English names for many fields like Group name and address/instructions.
- Differing area region codes
- Where does this come from?
- We have officially only 1 region here!
- Current database has 4 different regions for Finnish meetings there.
- What to do with old meeting info?
- The current database has one Swedish meeting there, should be deleted?
- We can add NAWS meeting data like Committee ID in our database before sending, in order to avoid duplicates.
- Some content is placed in different fields, like instructions to find the place etc. What is the right place for these?
- Some instructions are in ”Place”, some in ”Room”, some in ”Directions” and some even in ”LocBorough”.
- Some meetings have entered ”LocBorough”, but most have not. Officially we don’t use them as locational information here currently.
- Some meetings here are partly open, but we have to choose from open or closed.
- We can make dirty conversion for this, assume they are closed if not completely open.
- Also using a dirty conversion for wheelchair access, if no information given, assume no access.
- Currently if the meeting is Internet / Virtual, use true for wheelchair access.
- Does NAWS support UTF8? Scandinavian letters.
- We use ”More information” field for all other content, like instructions to find the place.
- This has to be broken to pieces and there might be no way for us to always do that properly, without the help of the group. And it’s in Finnish, so we have to do this manually.
- This means we really have to make a regional effort to make our meetings and groups compatible with the NAWS database.
- What to with internet / virtual meetings?
- They have completely different kind of addresses in use in our system. Addresses are replaced by join links.
- What to do when meeting information has changed?
- We can produce this excel automatically.
- One way to find out if stuff has changed, is to check to updated column and compare it to the last time the Excel document was sent to NAWS.
- BUT because some meetings might have sent information to NAWS but not to us, we might have need to cross-check by getting this Excel document back from NAWS and compare it to our database. This should be rare, but something to think about. But the most likely best scenario for us would be to add all NAWS fields to our database and fill them accordingly.