Closed ghost closed 9 years ago
Good idea, and practical, since it aligns us with what is actually tracked already. Hopefully they aren't too far off, since the AIRS Schema set the basic relationships, but you never know. Do we have access to each of them, or is this proprietary? If they are, maybe just a list, and not a schema?
We might not get the Schema - but getting a list of fields and field types would be good.
I wonder if Clive can reach out and ask the vendors for this as it would greatly increase the efficiency of this process.
I can give you ours as well - but need some time to grab it in a format that I can share.
Cool, maybe post them all to the wiki and link to them in these comments. Good stuff Mark. Way to cut to the chase!
Eric Jahn Data Architect/IT Director Alexandria Consulting LLC St. Petersburg, Florida 727.537.9474 alexandriaconsulting.com
On Wed, Aug 20, 2014 at 11:50 AM, Mark Perryman notifications@github.com wrote:
We might not get the Schema - but getting a list of fields and field types would be good.
I wonder if Clive can reach out and ask the vendors for this as it would greatly increase the efficiency of this process.
I can give you ours as well - but need some time to grab it in a format that I can share.
Reply to this email directly or view it on GitHub https://github.com/airs-linked-data/lov/issues/43#issuecomment-52798213.
Clive -
Can you reach out to the vendors and ask if they can please share:
Resource related Fields & Field Types
This will ultimately help us to create a tool that directly interfaces with their systems as well as to identify for us if we need to make any adjustments/additions.
This will ultimately help the vendors as we will be able to show them what the one to one relationship mapping is and how easy it will be to integrate.
Thanks,
Mark
Mark Perryman Project Manager
[image: Mail]
On Wed, Aug 20, 2014 at 8:53 AM, Eric Jahn notifications@github.com wrote:
Cool, maybe post them all to the wiki and link to them in these comments. Good stuff Mark. Way to cut to the chase!
Eric Jahn Data Architect/IT Director Alexandria Consulting LLC St. Petersburg, Florida 727.537.9474 alexandriaconsulting.com
On Wed, Aug 20, 2014 at 11:50 AM, Mark Perryman notifications@github.com wrote:
We might not get the Schema - but getting a list of fields and field types would be good.
I wonder if Clive can reach out and ask the vendors for this as it would greatly increase the efficiency of this process.
I can give you ours as well - but need some time to grab it in a format that I can share.
Reply to this email directly or view it on GitHub <https://github.com/airs-linked-data/lov/issues/43#issuecomment-52798213 .
— Reply to this email directly or view it on GitHub https://github.com/airs-linked-data/lov/issues/43#issuecomment-52798603.
If there are user defined fields, e.g., service preferences, would it be helpful to ask for information about what different organizations are using both for individual preferences and options (if there is a table)?
+1
The pilot has performed this task.
It might be easier if we ask to receive current examples of database schemas organizations are presently using so that we can map via one to one relationships to this model.
It could be beneficial to specifically receive a:
This will tell us if we are missing anything as well as help us to address the sufficiency of specific fields and whether or not we need to improve the field type for better classification, differentiation and attribution.
Thoughts?