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
From the years of experience of using FITS and C3PO, TU Wien will probably have conflict resolution rules that are reused often.
E.g. when two FITS tools export a slightly different date/time convention, or file format name to the FITS.XML.
Or there might be other FITS and C3PO users who have collected a 'knowledge base' of known resolvable conflicts.
E.g. at the National Archives of the Netherlands, we have learned what to look for (and what to ignore) when we see certain CONFLICTs in C3PO.
In the current version of C3PO, users will have to individually create conflict resolution rules.
Would it be possible to make rules exportable and importable, so that the FITS and C3PO user commuity can exchange reusable rules?
The text was updated successfully, but these errors were encountered:
From the years of experience of using FITS and C3PO, TU Wien will probably have conflict resolution rules that are reused often.
E.g. when two FITS tools export a slightly different date/time convention, or file format name to the FITS.XML.
Or there might be other FITS and C3PO users who have collected a 'knowledge base' of known resolvable conflicts.
E.g. at the National Archives of the Netherlands, we have learned what to look for (and what to ignore) when we see certain CONFLICTs in C3PO.
In the current version of C3PO, users will have to individually create conflict resolution rules.
Would it be possible to make rules exportable and importable, so that the FITS and C3PO user commuity can exchange reusable rules?
The text was updated successfully, but these errors were encountered: