How It Works
Credential Registry Infrastructure
User Community Support
Web Applications Hosting and Source Code
Reminder: The next Credential Engine Technical Advisory Group (TAG) webinar is scheduled for this Friday, May 25th at 11:00 am EST / 10:00 am CST / 9:00 am MT / 8:00 am PST.
- Briefing on UNESCO and OECD meetings in Paris on November 26-28, 2018
- Advancing the Pathways Terms Proposal
- Credential Registry
- Demo of the Quick Start Guides for Developers
- Publishing to and Consuming from the Registry
- Demo of the new Graph Search
- Account System Access to API Keys for Search now available
- Demo of accessing API Keys for Search
- Demo of using the new Search API endpoint
- Competency Connections
- Competency Connections through Condition Profile and Condition Manifest
- CE/CASS Updates
- Next Steps
Thank you to all TAG members that were able to participate in the October TAG meeting this past Friday, October 26, 2018.
Below are links to additional information related to the October TAG meeting.
- TAG Google Drive Folder - https://drive.google.com/drive/u/1/folders/1O9Uwqcirlykewot3SNxhbkwbiQ_MPzXk
- October 26, 2018 TAG Folder - https://drive.google.com/drive/u/3/folders/1h5G1UnJiYFR4EKutdEs0kr4C-_UTp9qp?ogsrc=32
- October 26, 2018 TAG Summary - https://docs.google.com/document/d/1SPFyNEgPgg5drJdqjCzqyKNi8WrqxtGi3ZoJmILChPM/edit?usp=sharing
- TAG Google Group - https://groups.google.com/forum/#!forum/credentialenginetech
Credential Engine strives to ensure our data meets the needs of all stakeholders, which sometimes requires updates to our technology infrastructure. Today, the information in the Credential Registry is being republished to fit a new data design. The data in the Registry will look the same when you access it on Credential Finder, but will allow for easier consumption by application developers.
In addition to this technology refresh, after gathering feedback and following our policy update protocol, we've added In Language to the minimum data policy; it will now be a required element for credentials, learning opportunities, and assessments. Any credential, learning opportunity, or assessment that is already published to the Registry will be automatically updated to include the language. However, anyone who has published to the Registry might use this opportunity to review their information and ensure it is up to date and accurate. We also encourage you to add more information to your existing credentials, or add new credentials to the registry.
As always, thank you for your continued support. If you have any questions, please direct them to email@example.com.
About Credential Registry
Credential Registry allows users to see what various credentials represent in terms of competencies, transfer value, assessment rigor, third-party approval status, and much more.
The open and voluntary registry will include all kinds of credentials, from education degrees and certificates to industry certifications, occupational licenses, and micro-credentials. Each credential will describe its name, type, level, competencies, assessments, accreditation, labor market value, and so on.
The goals are transparency and clarity, and to help align credentials with the needs of students, job seekers, workers, and employers.
Get Started Now
The Credential Engine project’s technical team (TT) provides credentialing pilot site partners with a set of services beneficial to each organization’s short- and long-term technology planning.
Through each phase of the Credential Engine project, the TT provides assistance, including non-technical and technical materials for administrators and technical staff.
Throughout the process, partners provide information and access needed to co-engineer the Credential Registry, Credential Directory, and other potential apps. Pilot site partners are also discovering the benefits of linked data, and providing iterative feedback on the process and outcomes.Learn More
Developers are able to leverage the the Credential Registry API to build applications that can read or publish as much or as little information about credentials as they need to.
The Credential Engine project's developers are using Dublin Core Application Profiles process to create systems that communicate all virtually all aspects of credentials.Learn More
Technical Advisory Committee
The Technical Advisory Committee (TAC) promotes collaboration across, and harmonization of, standardization initiatives that are developing data models, vocabularies, and schemas for credentials and competency frameworks, and related competency information such as criticality ratings and assessment data typically captured with a wide variety of systems.
The goal is to identify, document and openly share solutions that support comparability of credentials and competencies across industries/sectors, human resource systems, education, and government systems.Learn More
Easy to Use
The code base, data schema, and API endpoints are easy to use, and easy to learn. The code base is extensible, to make new features easier to add over time.
Source code, specs, and docs are all open. The system is designed to ensure metadata stays open, as well.
No server or API is 100% reliable, so the Credential Registry will distribute its metadata. It backs up data to archive.org, an organization dedicated to ensuring data never disappears.
Based on reseearch into metadata distribution by US Departments of Defense and Education, and many other organizations.
The Credential Registry is designed to scale horizontally by allowing communities to form independently and vertically to handle high demand.
Security is very hard to get right. We have deisgned an open metadata distribution system so that tight security is not necessary. We use cryptographic security within the open data itself to ensure organization identities are non-impersonable.