-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate group type data to group meta data #117
Comments
@ericknappe - Where are you at on this? For HASTAC we need a way to categorize groups, and it seems that the easiest way to do this is to use multiple group types rather than group metadata. This would keep society association as a group type, but add additional types to groups as needed. Is there a reason to move society association to group metadata rather than just adding additional group types as needed? |
I thought ARLIS had lost interest in this and did not know it was needed for HASTAC. The initial work is not extensive, getting the theme correct, might be tricky. Here's what I see as needed to change source of society id from group type to group meta value: Replace bp_groups_register_group_type with a custom function
Replace bp_groups_get_group_type with custom function
Modify logic to support society loops and society display
Write data migration script |
A new source of society ids will be needed to drive loops instead of bp group types. This could be one of the following:
It would be desirable to add attributes (type and status) to the current society definitions to control loop display which would lead to selecting option 2 in the short term. See the following example attributes that would come in handy.
|
Replacing bp_groups_get_group_type with something like get_group_society in the humanities-commons repo makes sense to me. I would prefer option 1 for getting a full list of society ids, though I see from your back-and-forth with Benn that there might be some issue there. We could have a statuc function in Humanities_Commons that returned a list of society ids. It could be hard-coded for now, and be replaced by a better option if the REST API can be made to work satisfactorily? |
Agreed. Although the GET (and caching) of COUs from the REST API does not cause a performance issue. The reason I'm currently using option 2 is that I'm using this additional metadata - status and type - which is not available in the current Comanage to filter COUs in certain contexts. |
A new source of society ids will be needed to drive loops instead of bp group types. This could be one of the following:
It would be desirable to add attributes (type and status) to the current society definitions to control loop display which would lead to selecting option 2 in the short term. See the following example attributes that would come in handy.
|
@mikethicke I have some more debugging to do on hcdev3 and feature branches to commit for 7 repos. This feature may be ready for testing after tonight. Looks like I'll also need to merge some changes from yesterday into 2 of the branches. |
Thanks @ericknappe --- there are other aspects of the HASTAC work that are taking longer than expected and we have a temporary solution without group types so this isn't super urgent. |
Is this still a thing? Should this be iceboxed or closed? |
@ericknappe is this still ongoing? Icebox or close if not? |
No description provided.
The text was updated successfully, but these errors were encountered: