Replies: 1 comment 2 replies
-
|
@gnyiri Appreciate your time and your suggestion. I think it would be a good idea to go on dealing with Templates rather than new DB fields. This would be be a long term solution and also a flexible approach. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your answer. Can we come up with a rough estimation (in man weeks) of implementing the Templates (incl. DB, backend, frontend + testing)? It would be really fine to know if its feasible for our next Call scheduled at September. |
Beta Was this translation helpful? Give feedback.
-
|
I would estimate roughly two weeks but this is with a developer that is experienced in the platform. I know that STFC is interested in the same feature so the easiest is for you to sync with them. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi there,
at ELI-ERIC we would need some new attributes for Technical Reviews (e.g. Cost of development, Lab use, Beam time, ...) for the next Call (September 2024).
What is the best approach to add these new fields if the other parties (ESS/STFC) are not interested or we cannot agree on the set of new fields in the short term? Even if we customize the backend through dep. injection, the frontend cannot be specialized (?).
My ideas to proceed:
Any thoughts?
Thanks in advance,
Gergely
Beta Was this translation helpful? Give feedback.
All reactions