While free-form Wiki usage to list our deployers works pretty well, we'd like to move to a primarily structured-data approach so that the data can be rendered as RSS, available for searching on attributes so deployers can seek like deployments, etc.
What data would go into a structured entry for a CAS deployer?
| data item |
quantity |
| Institution name |
1 |
| Address |
optional, useful for driving a Google Maps mashup? |
| CAS server version |
0 or 1 |
| Using proxy tickets, or not. |
optional boolean |
| CAS client libraries used. |
zero or more freetexts |
| Population served. |
one freetext |
| Hardware. |
one freetext |
| Date of CAS adoption. |
optional date |
| Login URL |
zero or more |
| Login screen snapshot image |
zero or more |
| URLs to institution-local documentation |
zero or more |
| Contacts |
zero or more people with associated URI, which might be an email address or a website |
| Extensions or modifications to CAS, if any. |
optional freetext |
| Future CAS plans |
optional freetext |
this list looks pretty good....we just need to make sure most of this is optional information
we don't want to make the CAS Server version a required field?