Last chance to register for COmanage Training
This is your last chance to register for COmanage training this spring.
Learn how to set up and administer COmanage Registry with this hands-on course. Follow the three common use cases to understand how to maximize your tool use: Enterprise Registry, Virtual Organization Registry, and Guest Registry. Learn how to de-duplicate your population data using a heuristic matching tool. Match can be used standalone or integrated into Registry. This hands-on workshop will provide you with the basics of developing and testing matching rules and strategies for testing these rules. This workshop also reviews how to use the Match API that you will use to integrate Match with your own tools.
Why COmanage Registry?ONE PERSON; ONE RECORD: Centralize data about your populations from your existing systems into single, aggregated person records; CUSTOM UNIQUE IDENTIFIER GENERATION: Produce unique identifiers for the people in your registry that can be relied upon across all of your systems, even when personal data have changed; SOPHISTICATED ENROLLMENT WORKFLOWS: Configure end-user-friendly invitation, conscription, and self-service enrollment workflows without writing a line of code or XML; MANAGE POPULATION GROUPS: Organize and manage your populations into groups to drive their roles and access provisions for your guest populations, virtual organizations, and enterprise; USE REGISTRY DATA IN OTHER SYSTEMS: Provision information aggregated and managed in your registry into other systems that need it; OFFBOARDING AUTOMATION: Configure offboarding policies to automate membership transitions and notify those who need to know; and EXPAND AND CUSTOMIZE: Use Registriy’s sophisticated and powerful plugin platform to connect, extend, and leverage your person-data to your unique systems, processes, and resources.
Why COmanage Match?MATCH ANYTHING: You define the attributes the tool will use to match. Match is optimized to match data about people, though it can be used to match records for any data set; RULES-BASED MATCHING: Build sophisticated matching algorithms based on fuzzy matches, dictionary-based matches, and substring matches — configure case sensitivity, the inclusion or exclusion of non-alphanumeric characters, and how NULL fields are handled; POTENTIAL AND CANONICAL MATCHES: High-confidence matches are automated — lower-confidence matches trigger notifications so they can be resolved in the Match interface or integrated system; IN THE MOMENT OR ASYNCHRONOUS: perform and resolve matches in the moment, or process matches in batches to be resolved later when needed; TOOL AGNOSTIC: Use Match as a stand-alone service, with COmanage Registry, or integrated into your own systems and workflows through a flexible API; and DESIGNED BY THE COMMUNITY FOR THE COMMUNITY: Match was created from a standard, the TAP Identity Match Protocol. This standard was collaboratively developed in 2021 by an Internet2 community working group led by Benn Oshrin, Managing Partner at SCG.
Q: Why did I get this awesome email? A: Because you have subscribed to one of the COmanage mailing lists! See the COmanage Email Lists wiki page for more details.
|