Open MichaelRBond opened 7 years ago
ddavisgraphics
commented
7 years ago Can you attach an image/wireframe of the interaction that needs to happen also? Typically you and I would draw it out on white boards in the office. I just want to make sure that I'm crystal clear on all things that this needs to do and that we do only what you need to get this working so we don't introduce any new bugs. Mainly because there is alot of JS that goes into making the "dynamic" form elements.
ddavisgraphics
commented
7 years ago Still a little confused on the Link Based On field.
Assuming that we have a check box that is clicked and marked true, a field will pop up with a dropdown menu. One that links to the Metadata Field and one that points to a field in the current object.
Why do we link a metadata field to any other object in the form aside from the object it is currently on? What would help is to identify what purpose the Link Based On fields are supposed to have in the end game and what type of data in needs to capture.
MichaelRBond
commented
7 years ago It is so that we can link objects together, based on fields.
For example.
If you have a book record. And then you have pages. You can link the pages to the book, based on metadata across objects.
It will allow more flexibility and fine grained control than a traditional parent/child relationship.
Get Outlook for iOShttps://aka.ms/o0ukef
From: David J. Davis notifications@github.com Sent: Monday, October 31, 2016 8:58:47 AM To: wvulibraries/mfcs Cc: Michael Bond; Author Subject: Re: [wvulibraries/mfcs] Additional Options for linked forms (#236)
Still a little confused on the Link Based On field.
Assuming that we have a check box that is clicked and marked true, a field will pop up with a dropdown menu. One that links to the Metadata Field and one that points to a field in the current object.
Why do we link a metadata field to any other object in the form aside from the object it is currently on? What would help is to identify what purpose the Link Based On fields are supposed to have in the end game and what type of data in needs to capture.
You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/wvulibraries/mfcs/issues/236#issuecomment-257287243, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABadrEl55ui--sWXV4_o5ZKmUqJXhA1bks5q5eYHgaJpZM4KBX4g.
ddavisgraphics
commented
7 years ago What are we counting as "objects" in this instance. The archived object A, and the archived object B? In that case the objects would have to be made before the form is made, which makes me wonder why it is defined in the form.
Or are we archiving based on Fields in an object?
When linking metadata forms to another form, we need the following new options.
1) Name -- Currently the field that is displayed in the dropdown is selectable, but we need to be able to make this a combination of fields.
2) We need a "Linked based on" option.
Example. A metadata form has a field called "bibid" and the parent object has a field called "bibid". We need to be able to so "Only display drop down options where bibid is equal on both forms"
it is possible that we will need to be able to do this using more than 1 field.
There should be a new check-box that hides/unhides this option. Each row should have an add/delete option on it, so that we can have as many matching options as required.
Each row should have 2 select boxes. 1 would be for the metadata form and 1 for the object form. Each dropdown would have all the non-array fields from the respective form. That way I could match up bibid on the metadata form to idno on the object form (or any other required mapping). I don't see any value in allowing multi-select forms to be selected.
This ticket will need additional back end work to make happen. Let me know when you have it finished, i'll take care of the backend work.