You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed that some people put a name with (co-Chair) in the name file of the comm file, because we have no way of representing different classes of members in the program committee. We know that chair and co-chair exist, but there may be other types in the future like "senior chair" or "advisory chair". For this reason we should have a field for role, and show whatever text is entered there next to the name.
The reason we need this is that I now fetch the comm.json file to insert into the program committee table on cryptodb. If I can't match the name and role, then it's difficult to match up to the database.
The text was updated successfully, but these errors were encountered:
I've noticed that some people put a name with (co-Chair) in the name file of the comm file, because we have no way of representing different classes of members in the program committee. We know that chair and co-chair exist, but there may be other types in the future like "senior chair" or "advisory chair". For this reason we should have a field for role, and show whatever text is entered there next to the name.
The reason we need this is that I now fetch the comm.json file to insert into the program committee table on cryptodb. If I can't match the name and role, then it's difficult to match up to the database.
The text was updated successfully, but these errors were encountered: