Feature/66 choose pj from db

bptlab / TracEX

This bachelorproject focuses on event log extraction from patient journeys using large-language models.

5 stars 5 forks source link

Feature/66 choose pj from db #115

Closed nils-schmitt closed 6 months ago

nils-schmitt commented 7 months ago

With this new feature you can now choose to extract a trace from the database. We have also added 10 real world patient journey from reddit to the database. You can now see the content of the patient journey after uploading/selecting it in the JourneyDetailView.

⚠️ Disclaimer: Some of the patient journey currently do not work because of timestamp issues. To some patient journeys I have added the date where the patient journey were published so that the pipeline works. You can now see

thangixd commented 7 months ago

I migrated the db and I still get this error. Do I have to to something else? Is this only on my side? Please let me know @nils-schmitt @tkv29

thangixd commented 7 months ago

I still get the errors (see above). But good job guys!

Why do we decide to automatically upload every patient journey to our database? But we need to decide if we want to save all tracers in our db?

And will there also be a possibility for the user to delete a patient journey in our app?

nils-schmitt commented 7 months ago

I still get the errors (see above). But good job guys!

Why do we decide to automatically upload every patient journey to our database? But we need to decide if we want to save all tracers in our db?

And will there also be a possibility for the user to delete a patient journey in our app?

Well there is already the possibility with the /admin view. And we save them, as this changes nothing and can easily be reverted. To delete a whole trace from the db is a little more tideous

tkv29 commented 7 months ago

PO Review✅ gj!

PitButtchereit commented 7 months ago

@tkv29 Since there are new changes with redirecting and there is a new Journey Detail View, please PO review again.

tkv29 commented 7 months ago

@PitButtchereit looking good!

thangixd commented 7 months ago

Can we perhaps achieve a better user experience if we don't have the same text twice in a row on the pages? How the filtering works is not yet relevant for the user here.

There should be another infobox instead of "The extraction pipeline helps you extract XES Event Logs from Patient Journeys. You can filter the results by event type and location before and after extraction to get exactly what you need."

something like:

[....] You can either upload a patient journey or select an existing journey from the database.

soeren227 commented 6 months ago

When extracting the twice from the same journey and trying to save both results to the db i get the following error:

PitButtchereit commented 6 months ago

@soeren227 I can not reproduce your error. Please show me on your machine.