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 think the app will read/rewrite the bib data file when a user submitted data. What will happen if two users are submitting at the same time?
The first question is, do we want to update the database with user input immediately? If we do want that, we need to have some lock mechanism to prevent write at the same time.
Otherwise, I think one approach could be:
maintain a database file in a separate location
if it's OK for user to see the existing references database, we can also show it inside the app with shiny DT.
user submitted records will be shown inside app as a pending update, with records, user name and some note field. This is also a good place to include the user note for each record if needed. The actual data can be saved as a csv file in a folder. So each user submission will create a file in that folder.
you can run a maintenance script to try to merge user submission with database from time to time, and only update the database when there is no error. This can be an automated job, and there will not be simultaneous write.
The text was updated successfully, but these errors were encountered:
I think I will probably switch to each ref being written to a separate file with a unique file name, instead of everything going in the same file. That should prevent any issues with records being overwritten. I want to keep the interface as simple and clean as possible, so I'm not keen on displaying all records that have already been submitted. It's easy enough to merge duplicate records at import time, so I'm not worried about that.
I think the app will read/rewrite the bib data file when a user submitted data. What will happen if two users are submitting at the same time?
The first question is, do we want to update the database with user input immediately? If we do want that, we need to have some lock mechanism to prevent write at the same time.
Otherwise, I think one approach could be:
The text was updated successfully, but these errors were encountered: