Welcome to the Visionlink: Indiana 2-1-1


Welcome!


Visionlink is proud to welcome another new customer, Indiana 2-1-1. These good folks have created a statewide solution that helps Hoosiers across Indiana find the local resources they need, 24 hours a day, 7 days a week. Additionally, aggregated and non-identified data is collected to assist communities in assessing needs and allocating resources.

We are pleased to support their work and will begin converting their data and using new API tools to assist their partnership efforts with other agencies and nonprofits across their fine state.

For additional information about 2-1-1 across the country, visit 211.us. To locate another 2-1-1 Center, visit 211.org.

Welcome aboard Indiana!

Popular posts from this blog

5 Billion Data Field Exchanges A Month

Image
What have we learned?Moving so many fields of data every month has taught us a few things. The first is that the structure of your data matters a great deal, particularly if you need data exchanges to be quick and inexpensive. To do that--one needs to structure the data correctly in the first place.

Dry topic? Sorry. Here is a fun animation to make it more interesting. Caution: the music starts up in scene three, and you'll be humming the tune later today. It's less than three minutes long. Check it out here:

https://support.communityos.org/vl-video
More detail on Data PointsWe track the traffic across our APIs by "data points" which is simply one data field exchanged one time. If a record with 50 fields on it is called 100 times, that would be 5,000 data points.

The amount of transferred data also depends on the amount of data in the fields that are exchanged or queried. Some fields may only have a few characters or a simple "yes" or "no." Other fiel…
Keep reading

New Password Standards

Image
None of us like passwords.Well, except for the good they do for us.

New research from NIST helps us to understand better ways to build passwords, and Visionlink has released an upgrade to its CommunityOS 2 platform in response.

The most fundamental change in the standards by NIST (National Institute of Standards and Technology), is about the frequency of forcing password changes. Survey says? Never.

That's right: in common use, requirements to change passwords every 30 or 180 days, as examples, result in less secure passwords.

The second major change concerns a previous recommendation to mix letters and numbers. Gone. And again, this is because the complexity causes real-world users to use passwords that can be broken too easily, and also because automated password breakers can easily deal with something like "st0rmC1ouds."

Repeated patterns (aaabbbccc) and sequences of adjacent keys on keyboards (jklnm), and common passwords are further examples of what we all should av…
Keep reading