Notes:

Technical Metadata SubgroupSome decisions about how to handle system properties were made, - use ebucore dates for system properties, - label vs use properties - addressed by PCDM PR#7

Some of the technical metadata properties in Fedora will be included in next release in a month or so

There is still discussion to have about a proposal from Aaron Coburn about handling the relationship between 'archival objects' and fits output

Action Items:

1. list of tools on tech md subgroup page - link to it from main metadata page.2. discuss Aaron's idea more, in one last tech md subgroup call next week

Applied Linked Data SubgroupFinalized dates for a linked data fragments sprint June 8 - June 19, 2015The first week of this sprint overlaps with Open Repositories conference in Indianapolis, anyone interested in working on linked data fragments at OR should contact Steven AndersonactiveFedora - there is an issue dealing with Solr, to allow atomic updates of individual properties - likely this will be looked at during the linked data fragment sprintNext call is May 28, 2015 at 9am PDTStill to discuss: how to integrate ld fragments with sidecar triplestore, how to a messaging driven way of updating Solr when sidecar triplestore is updated (vocabularies change)

Rights Metadata Subgroupmet two weeks ago - made a start on agreed list of predicatesnext meeting is immediately after this call

Descriptive Subgroup chaired by Carolyn Hansendecided to develop user stories describing use of descriptive metadatanot sure what the scope should be - how detailed should the user stories beKaren suggested that detailed user stories are not necessarily out of scopeperhaps collect in survey, decide whether or not to include in final set of user stories and therefore recommended best practices depending on demand/need.Should user stories be collected from hydra implementors, or end usersKaren suggests it is more of a focus on implementors.Corey suggested reaching out to hydra ux group and have a joint meeting, to find out if there are metadata elements needed by ux group that are missing.one goal is to develop a set of best practices - perhaps DPLA Application Profile style, with the understanding that not all implementations will need the same levels of detail.question around file level metadata - is this an area for descriptive or technical metadata?Sufia has an intermediate pcdm object, that wraps up all the files related to that object - extracted text, access copy, etc. Might want to augment file use vocabulary to capture relation between file and parent object?Suggestion to keep file level stuff out of descriptive metadata subgroup, to help avoid overloading this subgroup with extra deliverables.

Structural subgroupgood time to start on this post sufia sprint -this is a new group - call for members - looking for a facilitator - Karen will coordinate.perhaps wait until after rights subgroup to serialize the work a bit?Given active development going on (penn state, princeton) it might be good to put a call out and if there is not alot of uptake, that might be a sign to delay starting.Action Item:Karen Estlund to post a call for members and a facilitator to the hydra list.