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
Currently, the SpeziDataPipelineTemplate lacks functionality to monitor the active users in the database. There is no mechanism to detect when each user last connected or interacted with the system. This limitation makes it challenging to understand user engagement and activity patterns.
Solution
Implement a new feature in the SpeziDataPipelineTemplate to track the last activity date of each user in the database. This feature will work as follows:
The mechanism will scan the database to extract the last interaction date for each user. This can be achieved by identifying the date of the most recent FHIR resource collected for each user.
The feature will export this information into a CSV file. The CSV file can contain two columns: UserId and LastActivityDate.
Ensure that this new feature integrates with the existing pipeline processes and add tests to verify its proper functionality.
Additional context
No response
Code of Conduct
I agree to follow this project's Code of Conduct and Contributing Guidelines
The text was updated successfully, but these errors were encountered:
Sounds like an interesting feature. However, I had a few questions, regarding the input FHIR data. Would it be possible to receive access to a sample Firestore DB or more data to understand better and cover edge cases?
I also noticed there is sample_df.csv. From the source code, it seems to be a flattened_fhir_dataframe converted to a csv file. Would it be safe to make this assumption? I think it might be easier to work with the dataframe directly to implement the required functionality. What do you think?
Hi @ArnavS59, thanks for reaching out! You’re right—there are only few data points in the sample_df. If you're looking for more extensive data access, please contact @PSchmiedmayer to discuss this further and explore additional opportunities.
I created a PR for it in SpeziDataPipelineTemplate as requested.
To add tests, it seems that the function would need to imported into the main SpeziDataPipeline repo first.
Problem
Currently, the SpeziDataPipelineTemplate lacks functionality to monitor the active users in the database. There is no mechanism to detect when each user last connected or interacted with the system. This limitation makes it challenging to understand user engagement and activity patterns.
Solution
Implement a new feature in the
SpeziDataPipelineTemplate
to track the last activity date of each user in the database. This feature will work as follows:UserId
andLastActivityDate
.Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: