Motivation:<\/strong> We will use this pattern for visualizing quickly which is the state of our resources, or who has it assigned. One of the most frequent uses of this pattern is having people represented in lists and its assigned resources as cards. That information could flow between the different lists, but without any predetermined order. Lists could also be used for representing status of the resource, for example, when they don\u2019t follow an established order (as in a pipeline) or a determined sequence of steps.<\/p>\n\n\n\n Solution and graphic representation:<\/strong> Each list represents the state of the resource where it is assigned temporarily, or the person assigned as responsible of that information. The divisions representated with lists shouldn\u2019t follow any determined order. For example, if we represent people in lists, there mustn\u2019t be any precedence or hierarchical relationship between them. If we use this pattern for representing something more abstract, list shouldn\u2019t have a predetermined order as in a pipeline, where all activities are sequenced and follow a linear order. The resources represented in cards will flow between the different lists as they change their assigned person or their status.<\/p>\n\n\n\n Example:<\/strong><\/p>\n\n\n\n In this template we have a first list where the components of a music group are stored. The other two lists are two examples of pubs where concerts will be held. Artists will flow indistinctly to one pub or another, depending on where they play. Pubs will not be ordered by any criteria, and artists could flow completely free.<\/p>\n\n\n\n Related Patterns:<\/strong><\/p>\n\n\n\n This pattern is quite similar to \u201cInformation or resources lifecycle<\/a>\u201d, but without an established order between the lists. For this reason, “Information or resources lifecycle<\/a>\u201d is intended for representing pipelines or process with a determined order in their steps. With \u201cAssigned Information\u201d, the flow of the cards is unpredictable a priori and only depends on the real life factors that determine the assignment of the resource.<\/p>\n\n\n\n Trello Templates<\/strong> Examples:<\/strong><\/p>\n\n\n\n Problem:<\/strong>\u202fSituations or projects in which we need to organize information or resources whose classification could change over time.<\/p>\n\n\n\n Motivation:<\/strong> We will use this pattern for visualizing quickly which is the state of our resources, or who has it assigned. One of the most frequent uses of this pattern is having people represented in lists and its assigned resources as cards. That information could flow between the different lists, but without any predetermined order. Lists could also be used for representing status of the resource, for example, when they don\u2019t follow an established order (as in a pipeline) or a determined sequence of steps.<\/p>\n\n\n\n Solution and graphic representation:<\/strong> Each list represents the state of the resource where it is assigned temporarily, or the person assigned as responsible of that information. The divisions representated with lists shouldn\u2019t follow any determined order. For example, if we represent people in lists, there mustn\u2019t be any precedence or hierarchical relationship between them. If we use this pattern for representing something more abstract, list shouldn\u2019t have a predetermined order as in a pipeline, where all activities are sequenced and follow a linear order. The resources represented in cards will flow between the different lists as they change their assigned person or their status.<\/p>\n\n\n\n Example:<\/strong><\/p>\n\n\n\n In this template we have a first list where the components of a music group are stored. The other two lists are two examples of pubs where concerts will be held. Artists will flow indistinctly to one pub or another, depending on where they play. Pubs will not be ordered by any criteria, and artists could flow completely free.<\/p>\n\n\n\n Related Patterns:<\/strong><\/p>\n\n\n\n This pattern is quite similar to \u201cInformation or resources lifecycle<\/a>\u201d, but without an established order between the lists. For this reason, \"Information or resources lifecycle<\/a>\u201d is intended for representing pipelines or process with a determined order in their steps. With \u201cAssigned Information\u201d, the flow of the cards is unpredictable a priori and only depends on the real life factors that determine the assignment of the resource.<\/p>\n\n\n\n Trello Templates<\/strong> Examples:<\/strong><\/p>\n\n\n\n Problema:<\/strong>\u202fSituaciones o proyectos en los que necesitamos organizar informaci\u00f3n o recursos cuya clasificaci\u00f3n podr\u00eda cambiar con el paso del tiempo.<\/p>\n\n\n\n Motivaci\u00f3n:<\/strong> Usaremos este patr\u00f3n para visualizar r\u00e1pidamente cu\u00e1l es el estado de nuestros recursos, o qui\u00e9n lo tiene asignado. Uno de los usos m\u00e1s frecuentes de este patr\u00f3n es tener personas representadas en listas y sus recursos asignados como tarjetas. Esos recursos podr\u00edan fluir entre las diferentes listas, pero sin ning\u00fan orden predeterminado. Las listas tambi\u00e9n se pueden usar para representar el estado del recurso, por ejemplo, cuando estos no siguen un orden establecido (como en un pipeline).<\/p>\n\n\n\n Soluci\u00f3n y representaci\u00f3n gr\u00e1fica:<\/strong> Cada lista representa el estado del recurso al que est\u00e1 asignado temporalmente, o la persona asignada como responsable de esa informaci\u00f3n. Las divisiones representadas con las listas no deben seguir ning\u00fan orden determinado. Por ejemplo, si representamos a personas en las listas, no debe haber ninguna precedencia o relaci\u00f3n jer\u00e1rquica entre ellas. Si usamos este patr\u00f3n para representar algo m\u00e1s abstracto, la lista no deber\u00eda tener un orden predeterminado como en un pipeline, donde todas las actividades est\u00e1n secuenciadas y siguen un orden lineal (ver \"Information or resources lifecycle<\/a>\u201d). Los recursos representados en tarjetas fluir\u00e1n entre las diferentes listas a medida que cambien su persona responsable asignada o su estado (dependiendo de lo que queramos representar).<\/p>\n\n\n\n Patrones relacionados:<\/strong><\/p>\n\n\n\n Este patr\u00f3n es bastante similar al \u201cInformation or resources lifecycle<\/a>\u201d, pero sin un orden preestablecido entre las listas. Por este motivo, \"Information or resources lifecycle<\/a>\" est\u00e1 destinado a representar pipelines o procesos con un orden determinado en sus etapas. Con \"Assigned Information\", el flujo de las tarjetas es impredecible a priori y solo depende de los factores que en la vida real vayan determinando la asignaci\u00f3n del recurso.<\/p>\n\n\n\n Ejemplo:<\/strong><\/p>\n\n\n\n Con la plantilla \"Setlist Organizer\" podremos gestionar los componentes de un grupo de m\u00fasica y sus conciertos. As\u00ed, los m\u00fasicos inicialmente estar\u00e1n almacenados en la primera de las listas, e ir\u00e1n fluyendo al resto de listas, que representan los distintos conciertos previstos, en funci\u00f3n de si tocan o no en cada uno de ellos.<\/p>\n\n\n\n Ejemplos de Plantillas de Trello:<\/strong><\/p>\n\n\n\n Problem:<\/strong>\u202fSituations or projects in which we need to organize information or resources whose classification could change over time.<\/p>\n\n\n\n Motivation:<\/strong> We will use this pattern for visualizing quickly which is the state of our resources, or who has it assigned. One of the most frequent uses of this pattern is having people represented in lists and its assigned resources as cards. That information could flow between the different lists, but without any predetermined order. Lists could also be used for representing status of the resource, for example, when they don\u2019t follow an established order (as in a pipeline) or a determined sequence of steps.<\/p>\n\n\n\n Solution and graphic representation:<\/strong> Each list represents the state of the resource where it is assigned temporarily, or the person assigned as responsible of that information. The divisions representated with lists shouldn\u2019t follow any determined order. For example, if we represent people in lists, there mustn\u2019t be any precedence or hierarchical relationship between them. If we use this pattern for representing something more abstract, list shouldn\u2019t have a predetermined order as in a pipeline, where all activities are sequenced and follow a linear order. The resources represented in cards will flow between the different lists as they change their assigned person or their status.<\/p>\n\n\n\n Example:<\/strong><\/p>\n\n\n\n In this template we have a first list where the components of a music group are stored. The other two lists are two examples of pubs where concerts will be held. Artists will flow indistinctly to one pub or another, depending on where they play. Pubs will not be ordered by any criteria, and artists could flow completely free.<\/p>\n\n\n\n Related Patterns:<\/strong><\/p>\n\n\n\n This pattern is quite similar to \u201cInformation or resources lifecycle<\/a>\u201d, but without an established order between the lists. For this reason, \"Information or resources lifecycle<\/a>\u201d is intended for representing pipelines or process with a determined order in their steps. With \u201cAssigned Information\u201d, the flow of the cards is unpredictable a priori and only depends on the real life factors that determine the assignment of the resource.<\/p>\n\n\n\n Trello Templates<\/strong> Examples:<\/strong><\/p>\n\n\n\n![\"assigned](\"https:\/\/user-images.githubusercontent.com\/47741431\/110808758-96122e80-8284-11eb-9d0b-9b7a12452d2c.png\")
<\/a><\/figure><\/div>\n\n\n\n<\/figure><\/div>\n\n\n\nPattern:\u202fASSIGNED INFORMATION<\/h1>\n\n\n\n
<\/a><\/figure><\/div>\n\n\n\n<\/figure><\/div>\n\n\n\nPatr\u00f3n:\u202fASSIGNED INFORMATION<\/h1>\n\n\n\n
<\/a><\/figure><\/div>\n\n\n\n<\/figure><\/div>\n\n\n\nPattern:\u202fASSIGNED INFORMATION<\/h1>\n\n\n\n
<\/a><\/figure><\/div>\n\n\n\n<\/figure><\/div>\n\n\n\n