Right now the suggestion field is hard-coded based on the pitfall or warning id and identical for any repository.
With @vuillaut, we identified multiple pitfalls and warnings whose suggestions could be automatically personalized from the somef output.
Here is the list of pitfalls and warnings (yes means that the suggestion can be automatically defined for the current analyzed repository):
- P001 - yes
- P002 - no
- P003 - probably ?
- P004 - yes
- P005 - no
- P006 - maybe ?
- P007 - yes
- P008 - no
- P009 - yes
- P010 - no
- P011 - yes (in majority of cases)
- P012 - yes
- P013 - no
- P014 - yes (in most cases)
- P015 - no
- P016 - yes
- P017 - yes
- P018 - yes
- W001 - no
- W002 - yes
- W003 - yes
- W004 - yes in most cases ?
- W005 - yes
- W006 - yes
- W007 - maybe
- W008 - yes
- W009 - no
- W010 - yes
these indicators should be added to RSMetaCheck table here
In addition, we can then suggest the metadata files generated by somef as a solution for most of these cases.
Right now the suggestion field is hard-coded based on the pitfall or warning id and identical for any repository.
With @vuillaut, we identified multiple pitfalls and warnings whose suggestions could be automatically personalized from the somef output.
Here is the list of pitfalls and warnings (yes means that the suggestion can be automatically defined for the current analyzed repository):
these indicators should be added to RSMetaCheck table here
In addition, we can then suggest the metadata files generated by somef as a solution for most of these cases.