Hi Franck,
We ran into a similar issue (if I understand correctly) in the context of importing notes. If you’re talking about a note field in your template, it should be possible to store that field in the same way as for the ISAD template. This issue ticket might help:
https://projects.artefactual.com/issues/6143
(and see also the linked issue which has a bit more about the type_id values in the note table)
Briefly, there’s a similar issue to what you might be describing between the RAD and ISAD templates, but the ISAD and DACS templates are OK.
Fields plural is probably more complicated.
Tim
Tim Hutchinson
Head, University Archives & Special Collections
University Library, University of Saskatchewan
Tel: (306) 966-6028 Fax: (306) 966-6040
Email: tim.hut...@usask.ca
--
You received this message because you are subscribed to the Google Groups "Qubit Toolkit Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
qubit-dev+...@googlegroups.com.
To post to this group, send email to
qubi...@googlegroups.com.
Visit this group at http://groups.google.com/group/qubit-dev.
For more options, visit https://groups.google.com/d/optout.
Hi Franck,
I’d be nervous about actually migrating data unless there’s a one-to-one mapping. What would happen if the template gets changed back?
In 2.x, it is also possible to set the default display template for any description. In that case your custom template would still be displayed (for those descriptions) even if the default template had changed.
I think you’re right that the original template reference doesn’t get stored, but you could check for the relevant fields being populated.
Tim
--