Bug 6039 - move meta-data translation strings (submission.xml) to plug-ins
move meta-data translation strings (submission.xml) to plug-ins
Status: NEW
Product: OJS
Classification: Unclassified
Component: Authors
2.4.x
PC Linux
: P3 normal
Assigned To: PKP Support
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-10-14 10:25 PDT by jerico
Modified: 2012-09-21 13:13 PDT (History)
2 users (show)

See Also:
Version Reported In:
Also Affects:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jerico 2010-10-14 10:25:50 PDT
* make sure they're included just by instantiating the schema (to avoid loading of plug-in category for translations to be available)
* make sure that we have some way of mapping fields across schemas and make sure that it's the mapping that is named, not the fields (as only the mapping is relevant to the end user). Such a mapping contains all translation strings for the field (display name, validation message) as well as a 1:1 attribution to a field in our application model as defined by the corresponding meta-data adapter. Maybe such a mapping should therefore be provided by the adapter? The mapping is also used for users to customize available meta-data fields on set-up. They'll only say which fields to map, if these fields are mapped in several schemas then they'll automatically be available in both schemas. Such a mapping could also resolve the somehow awkward solution via assoc types that we have right now in the schema.