You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I sent this note to the group that showed interest:
Hi All!
You're receiving this email because you either tagged yourself, or were tagged by someone else at the DCP Workshop last week. We are hoping to make practical progress regarding making best use of the DATS format, and finding places to share code for managing the task of metadata indexing.
Are you available at the normal KC7 time (Thursday 9-10am pacific) next week? I think it's a natural time, but here is a doodle poll to fill out if we can't find consensus on that time.
If someone is a Zoom master and wants to take over hosting the actual conference (and recording it for others), I'd appreciate it. Otherwise, we'll meet on hangouts.
And don't worry if you can't make it, we'll make the notes and anything useful learned available to the rest of KC7!
I'm basically looking for instruction from the folks who have used DATS and JSON-LD how we can easily write and share code for denormailzing DATS into documents for indexing: #3
To that end, if folks could come with:
DATS related code concepts/use cases
SPARQL queries against DATS
Suggestions for ETL processes (triple stores?)
DBGap scraping/export techniques
ElasticSearch mappers/analyzers
I believe everyone on this list had something to say about one of these things. Thanks for taking the extra time to help us figure out places to share code!
I'll offer a brief case study of how we use ElasticSearch to present detailed information about a project. One of the conceptual blockers that I would like the communities help to be able to formulate properly to KC2 and 7 groups is about the "resolution" or "granularity" of metadata and unique identifiers. Should the DATS model be expected to contain information on how to resolve individual data objects per dataset, or is it a metadata representation of the project at a higher level? What is expected in terms of harmonization of variables, versus column names?
Best!
David
The text was updated successfully, but these errors were encountered:
At the DCP workshop one of the breakout groups discussed metadata modeling, and we would like to continue that conversation with a little more code.
Please add your notes on what you expect from this followup, and any links that would help structure conversation.
Add yourself to this poll (and make sure I can get your contact info) if you're interested!
https://doodle.com/poll/4mtaeps9kp2pnqzh
I sent this note to the group that showed interest:
Hi All!
You're receiving this email because you either tagged yourself, or were tagged by someone else at the DCP Workshop last week. We are hoping to make practical progress regarding making best use of the DATS format, and finding places to share code for managing the task of metadata indexing.
Are you available at the normal KC7 time (Thursday 9-10am pacific) next week? I think it's a natural time, but here is a doodle poll to fill out if we can't find consensus on that time.
https://doodle.com/poll/4mtaeps9kp2pnqzh
If someone is a Zoom master and wants to take over hosting the actual conference (and recording it for others), I'd appreciate it. Otherwise, we'll meet on hangouts.
And don't worry if you can't make it, we'll make the notes and anything useful learned available to the rest of KC7!
I'm basically looking for instruction from the folks who have used DATS and JSON-LD how we can easily write and share code for denormailzing DATS into documents for indexing: #3
To that end, if folks could come with:
I believe everyone on this list had something to say about one of these things. Thanks for taking the extra time to help us figure out places to share code!
I'll offer a brief case study of how we use ElasticSearch to present detailed information about a project. One of the conceptual blockers that I would like the communities help to be able to formulate properly to KC2 and 7 groups is about the "resolution" or "granularity" of metadata and unique identifiers. Should the DATS model be expected to contain information on how to resolve individual data objects per dataset, or is it a metadata representation of the project at a higher level? What is expected in terms of harmonization of variables, versus column names?
Best!
David
The text was updated successfully, but these errors were encountered: