Difference between revisions of "WBConfCall 2024.11.07-Agenda and Minutes"
| (5 intermediate revisions by 2 users not shown) | |||
| Line 2: | Line 2: | ||
====Help-desk==== | ====Help-desk==== | ||
| − | + | * https://github.com/WormBase/website/issues/9610 Fasciola hepatica database for Reactome Analysis? | |
| − | + | * janelia.hhmi.org access to WB blocked? | |
| + | |||
| + | * Keep submitter email in Github for future contact? | ||
| + | |||
| + | |||
| + | ====AGR==== | ||
| + | Alliance Member Data Pipeline Progress: https://docs.google.com/spreadsheets/d/1DnwSsmauu-ad7x4S8PuV2-qL3P3Y1dbw086EqF92t-c/edit?usp=sharing | ||
== Minutes == | == Minutes == | ||
| + | === AI Summary === | ||
| + | (edited by Raymond) | ||
| + | |||
| + | |||
| + | ====Reactome Tool and Wormbase Issues==== | ||
| + | |||
| + | The team discussed issues related to the Reactome analysis tool and a connection problem with Wormbase. Raymond noted that he had not received a response from the user about their needs for Reactome, and the issue with Wormbase was being handled by Todd. There was also a discussion about the help desk, with Raymond suggesting that they keep the full email addresses of submitters in Github Tickets to facilitate communication. The team agreed to wait for Todd to resolve the Wormbase issue, and to wait for further clarification of needs from the user about Reactome. | ||
| + | |||
| + | ====Email Addresses in Github Tickets==== | ||
| + | |||
| + | The team discussed the privacy and compliance issues related to email addresses in their Github tickets. Stavros suggested that it's not difficult to find the original poster's email in saved personal inbox. Chris recalled that they had previously hidden email addresses to prevent them from being publicly visible in their issue tracker, but now that the issue tracker is private, this may no longer be necessary. Raymond agreed, suggesting that since they are keeping the Github ticket, it makes more sense to keep all the information there, including email addresses. Raymond has been doing that by manually entering the addresses. The team decided to discuss this further with Todd. | ||
| + | |||
| + | ====Alliance Member Data and Pipeline Progress==== | ||
| + | |||
| + | In the meeting, Stavros discussed the final year's agenda, which included a new item on alliance member data and pipeline progress. Stavros presented a table detailing the number of objects in various instances, including databases like geneace and camace. He also checked the last time each class was curated and the number of objects in those classes. Chris appreciated this information and planned to review it further. Stavros also mentioned that he had used this data to understand the state of certain classes, and he was open to further inquiries. Chris also expressed his need to refresh his memory on the pipelines. | ||
| + | |||
| + | ====WS294 Class Counts and Builds==== | ||
| + | |||
| + | Chris and Stavros discussed the counts in the WS294 classes, with Stavros clarifying that the greatest number of objects should be in the build database, unless something is filtered during the build. The team also acknowledged Wen's contribution to curating the gene-allele connections. | ||
Latest revision as of 18:01, 7 November 2024
Contents
Agenda
Help-desk
- https://github.com/WormBase/website/issues/9610 Fasciola hepatica database for Reactome Analysis?
- janelia.hhmi.org access to WB blocked?
- Keep submitter email in Github for future contact?
AGR
Alliance Member Data Pipeline Progress: https://docs.google.com/spreadsheets/d/1DnwSsmauu-ad7x4S8PuV2-qL3P3Y1dbw086EqF92t-c/edit?usp=sharing
Minutes
AI Summary
(edited by Raymond)
Reactome Tool and Wormbase Issues
The team discussed issues related to the Reactome analysis tool and a connection problem with Wormbase. Raymond noted that he had not received a response from the user about their needs for Reactome, and the issue with Wormbase was being handled by Todd. There was also a discussion about the help desk, with Raymond suggesting that they keep the full email addresses of submitters in Github Tickets to facilitate communication. The team agreed to wait for Todd to resolve the Wormbase issue, and to wait for further clarification of needs from the user about Reactome.
Email Addresses in Github Tickets
The team discussed the privacy and compliance issues related to email addresses in their Github tickets. Stavros suggested that it's not difficult to find the original poster's email in saved personal inbox. Chris recalled that they had previously hidden email addresses to prevent them from being publicly visible in their issue tracker, but now that the issue tracker is private, this may no longer be necessary. Raymond agreed, suggesting that since they are keeping the Github ticket, it makes more sense to keep all the information there, including email addresses. Raymond has been doing that by manually entering the addresses. The team decided to discuss this further with Todd.
Alliance Member Data and Pipeline Progress
In the meeting, Stavros discussed the final year's agenda, which included a new item on alliance member data and pipeline progress. Stavros presented a table detailing the number of objects in various instances, including databases like geneace and camace. He also checked the last time each class was curated and the number of objects in those classes. Chris appreciated this information and planned to review it further. Stavros also mentioned that he had used this data to understand the state of certain classes, and he was open to further inquiries. Chris also expressed his need to refresh his memory on the pipelines.
WS294 Class Counts and Builds
Chris and Stavros discussed the counts in the WS294 classes, with Stavros clarifying that the greatest number of objects should be in the build database, unless something is filtered during the build. The team also acknowledged Wen's contribution to curating the gene-allele connections.
