The design of the feature is complete but since it will be backwards incompatible it has been tagged for version 3.0.
The good news is that the design will use dynamic forms and thus the problems of the display widget is also solved. This means that the new metadata type definition code will specify how data is stored as well as how it will be displayed and edited by the user. This opens the possibility for the usual data types like numbers, floats, dates but also custom data types. The only part still being worked to solved if how to type cast the data internally to support full text searching. On Wednesday, July 19, 2017 at 12:37:38 AM UTC-4, Mark Phillips wrote: > > Roberto, > > Any updates? > > Thanks, > > Mark > > On Sun, Jul 9, 2017 at 10:16 PM, Mark Phillips <[email protected] > > wrote: > >> Thanks! >> >> On Sun, Jul 9, 2017 at 11:47 AM, Roberto Rosario >> <[email protected]> wrote: >> >>> I've been going over this issue and will be trying a few ideas in the >>> next development cycle. >>> >>> On Friday, June 9, 2017 at 6:46:43 PM UTC-4, Mark Phillips wrote: >>>> >>>> Issue #139 - https://gitlab.com/mayan-edms/mayan-edms/issues/139 >>>> >>>> Issue #178 (referenced in issue #139) - >>>> https://gitlab.com/mayan-edms/mayan-edms/issues/178 >>>> >>>> My original email from 10/2/2015: >>>> Is there a way to allow multiple selections from a metadata field? >>>> >>>> For example, say there is a metadata field called People defined as >>>> {"Peter", "Paul", "Mary"}. When I try to add the People metadata to a >>>> document, I can only select one name from the list. I would like to be >>>> able >>>> to select one, two, or three of the names and add these as metadata to the >>>> document. Think of a collection of photographs or people. One would like >>>> to >>>> have the names of all the people in the photograph associated with that >>>> photograph. >>>> >>>> If I cannot make multiple selections from the People metadata, how >>>> would I achieve my goal using what Mayan has to offer? >>>> >>>> Finally, Mathias Behrle responded to my email with this link - >>>> https://github.com/mayan-edms/mayan-edms/issues/177#issuecomment-90167288 >>>> >>>> Thanks for looking into these issues. >>>> >>>> Mark >>>> >>>> On Fri, Jun 9, 2017 at 1:11 PM, Roberto Rosario <roberto.ros.....@ >>>> gmail.com> wrote: >>>> >>>>> Can you add a link to the issues you are referring, I'm checking issue >>>>> #139 and #178 and can't see the relationship between them. Some issues >>>>> number might not make sense since they were migrated from Github to >>>>> Gitlab >>>>> and something could have been lost in the process. >>>>> >>>>> >>>>> On Friday, June 2, 2017 at 6:30:12 PM UTC-4, Mark Phillips wrote: >>>>>> >>>>>> Roberto, >>>>>> >>>>>> I submitted issue #139 to you quite a while ago, and I see that one >>>>>> of the prerequisites has been closed (Issue #178). Does this mean that >>>>>> #139 >>>>>> can be implemented now? Or are there other issues standing in the way? I >>>>>> need #139 on a current project of mine, and would like to use Mayan for >>>>>> this project. >>>>>> >>>>>> Is there a work around for issue #139? >>>>>> >>>>>> Thanks! >>>>>> >>>>>> Mark >>>>>> >>>>> -- >>>>> >>>>> --- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "Mayan EDMS" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> -- >>> >>> --- >>> You received this message because you are subscribed to the Google >>> Groups "Mayan EDMS" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> > -- --- You received this message because you are subscribed to the Google Groups "Mayan EDMS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
