I spoke with @VivianChu about this already, but would like @hweng and @lsitu to look into this as well.
Essentially, I would like for us to evaluate where the team feels we might be better off starting fresh with a new Hyrax repo, reviewing the newly supported features/patterns, and then considering how and what to port in. I'm particularly interested in the Collections Extension Working Group work as well that should be folded into the final Hyrax 2.0 release. Please chat with @dt-ucsd for more info on that. If each of you can take some time to R&D on this that would be great, and then we can convene as a group and discuss what we think is best.
Rationale
It may prove valuable in the long run to port our existing codebase that has gone from being based on Curation Concerns -> Sufia -> Hyrax (multiple versions) to a new clean Hyrax 2.0 codebase. Presumably, if we decided to do this, we would wait for an official 2.0 release.
Descriptive summary
I spoke with @VivianChu about this already, but would like @hweng and @lsitu to look into this as well.
Essentially, I would like for us to evaluate where the team feels we might be better off starting fresh with a new Hyrax repo, reviewing the newly supported features/patterns, and then considering how and what to port in. I'm particularly interested in the Collections Extension Working Group work as well that should be folded into the final Hyrax 2.0 release. Please chat with @dt-ucsd for more info on that. If each of you can take some time to R&D on this that would be great, and then we can convene as a group and discuss what we think is best.
Rationale
It may prove valuable in the long run to port our existing codebase that has gone from being based on Curation Concerns -> Sufia -> Hyrax (multiple versions) to a new clean Hyrax 2.0 codebase. Presumably, if we decided to do this, we would wait for an official 2.0 release.
Related work
143