Change Details

ToDo: [x] Add query parameter to request base types in citoid and temporarily include both basefield and specific fields to allow for gradual update of templatedata. [x] In extension, request basefields parameter. [] Update templateData for cite web or equivalent everywhere [x] en wiki Options: Option 1: Change how TemplateData is done such that we allow the listing of multiple citoid parameters that are allowed. Cons: Makes templateData more difficult to write and read. Also not exactly sure how to denote that since we are already using lists to mean something else... objects maybe? Gets very complicated to fit into existing structure. Requires existing templateData to be updated, will cause service interruption. Pros: Universal solution Option 2: Allow a query to request the base type (i.e. publicationTitle instead of bookTitle or websiteTitle, for example) Cons: Doesn't solve every issue. Requires templateData to be updated; will cause service interruption. Pros: Solves issue for two cases a bug was filed for, doesn't drastically change how the service works. Option 3: Create a new template for every type where this presents a problem, and give it different template data. Pros: Universal solution, won't causing any service interruption. Cons: Community might not like new templates being created/inserted - possible maintenance burden on community. Code duplication.

ToDo: [x] Add query parameter to request base types in citoid and temporarily include both basefield and specific fields to allow for gradual update of templatedata. [x] In extension, request basefields parameter. [] Update templateData for cite web or equivalent everywhere [x] en wiki [x] fr Options: Option 1: Change how TemplateData is done such that we allow the listing of multiple citoid parameters that are allowed. Cons: Makes templateData more difficult to write and read. Also not exactly sure how to denote that since we are already using lists to mean something else... objects maybe? Gets very complicated to fit into existing structure. Requires existing templateData to be updated, will cause service interruption. Pros: Universal solution Option 2: Allow a query to request the base type (i.e. publicationTitle instead of bookTitle or websiteTitle, for example) Cons: Doesn't solve every issue. Requires templateData to be updated; will cause service interruption. Pros: Solves issue for two cases a bug was filed for, doesn't drastically change how the service works. Option 3: Create a new template for every type where this presents a problem, and give it different template data. Pros: Universal solution, won't causing any service interruption. Cons: Community might not like new templates being created/inserted - possible maintenance burden on community. Code duplication.

ToDo: [x] Add query parameter to request base types in citoid and temporarily include both basefield and specific fields to allow for gradual update of templatedata. [x] In extension, request basefields parameter. [] Update templateData for cite web or equivalent everywhere [x] en wiki [x] fr Options: Option 1: Change how TemplateData is done such that we allow the listing of multiple citoid parameters that are allowed. Cons: Makes templateData more difficult to write and read. Also not exactly sure how to denote that since we are already using lists to mean something else... objects maybe? Gets very complicated to fit into existing structure. Requires existing templateData to be updated, will cause service interruption. Pros: Universal solution Option 2: Allow a query to request the base type (i.e. publicationTitle instead of bookTitle or websiteTitle, for example) Cons: Doesn't solve every issue. Requires templateData to be updated; will cause service interruption. Pros: Solves issue for two cases a bug was filed for, doesn't drastically change how the service works. Option 3: Create a new template for every type where this presents a problem, and give it different template data. Pros: Universal solution, won't causing any service interruption. Cons: Community might not like new templates being created/inserted - possible maintenance burden on community. Code duplication.