Extension of the schema: internal data block

[bschweighofer]

Could the openCost schema be extended so that it can also be used for internal data entry (no external transfer)? This would avoid duplication of data entry.

ReportBy: online discussion 2/3/23

[aw-bib]

At join² our internal data block is also a superset of openCost, IOW we hold more data than we expose in openCost and IMHO this will always be the case, as e.g. local accounting numbers should not be exposed to the outside world. So I think the local storage format, that is most likely dependent on the local system used (e.g. in join² it is based on Marc21-Holdings), is a bit out of the scope of openCost.

OTOH I deem it a valuable discussion in the openCost context to also collect which internal values are usually stored and kept:

• For new users this would give a valuable guideline oh, I should store x, but why? just because you need it for X in a year...
• It might also reveal some values that escaped us that are relevant for the transfer format.

[Geomarbibliothek]

We would also like to keep information like aw-bib mentioned (local accounting numbers; which department paid e.g.) intern - and of course would like to put them into the system only once! So, yes, it would be good to be able to use some of the entry only for internal use.