Time/Place

This meeting is a hybrid teleconference and IRC chat. Anyone is welcome to join...here's the info:

Time: 11:00am Eastern Daylight Time US (UTC-4)
U.S.A/Canada toll free: 866-740-1260, participant code: 2257295
International toll free: http://www.readytalk.com/intl
- Use the above link and input 2257295 and the country you are calling from to get your country's toll-free dial-in number
- Once on the call, enter participant code 2257295
IRC:
- Join the #fcrepo chat room via Freenode Web IRC (enter a unique nick)
- Or point your IRC client to #fcrepo on irc.freenode.net

Attendees

Retiring m2.duraspace.org
Server-managed Premis predicates:
1. Use case: https://s3.amazonaws.com/uploads.hipchat.com/267943/1716525/5cfgR9Zs70FjXrY/sparql2
2. Blocked by: https://github.com/fcrepo4/fcrepo4/blob/master/fcrepo-kernel-api/src/main/java/org/fcrepo/kernel/api/RdfLexicon.java#L137
ModeShape and many-child-nodes... almost perfect: https://github.com/ModeShape/modeshape/pull/1459

Bug Prioritization

type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Tickets resolved this week:

key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution
Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Tickets created this week:

key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution
Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Hosts a number of Maven artifacts that Fedora 3 needs
We would like to retire it
One approach: retire very soon and offer a script and JAR files to build the latest version of Fedora 3
Another option: Continue maintaining the server (not very appealing)
- Someone else could stand up the server on their own infrastructure and redirect the DNS
We could send a post to the mailing list asking if anyone wants to maintain the server
There are probably very few people interested in building Fedora 3 vs. just using the installer
- For these people, will Andrew’s build script work as an option?

There are some server-managed predicates in Fedora 4 now
In some cases users want to manage their own PREMIS properties but they are currently immutable
Should we stop using non-Fedora predicates for server-managed properties?
We have to reserve some LDP properties, though many can be updated via SPARQL-Update
In the case of PREMIS/fixity, should we (1) use a Fedora namespace, or (2) continue to use PREMIS but allow the properties to be mutable?
Recommendation: Investigate allowing fixity-related properties to be user-modified
- Longer-term: Investigate using a server-managed Fedora namespace instead of PREMIS