[Ig-fedora] Fedora in the CLARIN infrastructure

[David Wilcox]

Hi Felix,

I’m glad to hear you’re making progress with testing Fedora 6 and the migration utility. I checked with the Fedora tech leads regarding your issue and they said they would likely be able to help you resolve it - they just need a few more details.

Can you create an issue in the Fedora JIRA [1] that includes a detailed description of the issue (e.g. information on your Fedora 3 external datastreams, the Fedora 6 stack trace, etc.)? Let me know if you do not already have an account and I will create one for you (the JIRA and Confluence wiki can be accessed using the same account). 

Regarding the API, there are no anticipated changes at this point. The search API is a new addition in Fedora 6.0 but it does not alter the existing API, which remains compatible with the published specification and Fedora 5.x.

Let me know if you run into any other issues - I’m sure the tech team would be happy to help you resolve problems as they arise. We plan to release an Alpha next week, which will be mostly feature complete, and a Beta is expected by the end of the year.

Regards,

David 

[1] https://jira.lyrasis.org/browse/FCREPO

> On Nov 6, 2020, at 10:27 AM, Felix Helfer <helfer at informatik.uni-leipzig.de> wrote:
> 
> Hi David,
> 
> I can report some progress with the testing here at the Leipzig centre. We successfully built and deployed a Fedora 6 instance from the git repo over our Fedora 3.7.1 repo data which was exported via the migration tool. On a first glance, all resources seem to be accounted for (we will perform some more in-depths checks of this soon). 
> 
> The only problem we encountered so far is with the migration of external datastreams (of which we have a sizeable amount). Resources migrated to the F6 repo which had such external datastreams in the F3 repo do still have a reference to a corresponding child node - but trying to access this child resource results in an internal server error. Can you give any insight into the handling of external datastreams in the migration process? I am aware that we might be more of an outlier here among users, but it would be valuable information to us whether this will be supported in any way (or already is, and I just overlooked something). 
> 
> As we plan on starting to develop some initial tools to interact with the repository, I also wanted to ask if you can guarantee that the API will, at this point, not undergo any significant future changes? As I remember, this is not really the focus of this version update anyway, but I just want to make sure before we begin any major development work.
> 
> I will of course let you know of any new developments or insights as we continue testing the F6 repository and the data migration. 
> 
> Best regards,
> Felix
> 
> 
> Am 05.10.20 um 21:49 schrieb David Wilcox:
>> Hi Thomas,
>> 
>> I met with the tech leads to discuss your Fedora requirements - while an OAI-PMH interface is not on the roadmap for an initial 6.0 release, it could be added as a module soon afterward. I’d like to get a sense of who else in the community might have such a requirement, so I will bring it up at this week’s tech call and post a message to the community mailing list asking if others have a need for a OAI-PMH module at the Fedora level. Once we determine the level of interest and available resources we can discuss how best to implement this feature.
>> 
>> In the meantime, it would be great if your team could schedule some time for testing and report back to us. The migration tool should be able to migrate your Fedora 3.x content to a format compatible with Fedora 6.x, and you should be able to view and browse this data using the latest Fedora 6.x build. 
>> 
>> The migration tool can be found here: https://github.com/fcrepo-exts/migration-utils <https://github.com/fcrepo-exts/migration-utils>. You’ll need to build it using Maven and Java 11.
>> 
>> Similarly, you can build Fedora 6.x using the main branch in this repository: https://github.com/fcrepo/fcrepo <https://github.com/fcrepo/fcrepo>. Instructions are in the Readme. Or you can use the Fedora Docker: https://github.com/fcrepo-exts/fcrepo-docker <https://github.com/fcrepo-exts/fcrepo-docker>.
>> 
>> Let me know if any of the instructions are unclear or if you run into any issues. We are quickly approaching an Alpha release so we will have packaged releases available for testing soon as well.
>> 
>> Regards,
>> 
>> David
>> 
>>> On Sep 17, 2020, at 4:17 PM, David Wilcox <dwilcox at duraspace.org <mailto:dwilcox at duraspace.org>> wrote:
>>> 
>>> Hi Thomas,
>>> 
>>> Thanks very much for sharing this document - it is nice to have a brief summary of your requirements for Fedora 6.x. I have a meeting with the technical leads on Monday so I will share this document with them and we will discuss how best to respond to your requirements. I’ll get back to you with some ideas, along with instructions on how best to test the migration tool and Fedora development versions and report your results. The software is quickly approaching an Alpha release so your testing and feedback will be timely.
>>> 
>>> Regards,
>>> 
>>> David
>>> 
>>>> On Sep 17, 2020, at 10:42 AM, Thomas Eckart <teckart at informatik.uni-leipzig.de <mailto:teckart at informatik.uni-leipzig.de>> wrote:
>>>> 
>>>> Hello David,
>>>> 
>>>> as promised we have discussed in CLARIN our requirements for a repository solution. You can find the resulting document attached. It shouldn't be very surprising, as it just sums up the points we already talked about in our video conference in June. Feel free to ask if something needs clarification.
>>>> 
>>>> As Felix already mentioned at last week's users meeting, we have established an interest group of Fedora users in CLARIN.
>>>> Its mailing list (CC'd) is meant for internal coordination and help but also as a contact point for you, in case of questions or a need for feedback.
>>>> 
>>>> I hope we can keep up the good communication between CLARIN and the Fedora team. We are happy to help if you need any feedback. We also should have some capacities to test Fedora development versions or new versions of the migration tool.
>>>> 
>>>> Best,
>>>> Thomas
>>>> 
>>>> 
>>>> 
>>>> -- 
>>>> Thomas Eckart
>>>> Natural Language Processing Group
>>>> Department of Computer Science
>>>> University of Leipzig
>>>> Augustusplatz 10
>>>> 04109 Leipzig, Germany
>>>> <CLARIN Requirements Fedora.pdf>
>>> 
>> 
> 
> -- 
> Felix Helfer
> Natural Language Processing Group
> Department of Computer Science
> University of Leipzig
> Augustusplatz 10
> 04109 Leipzig, Germany

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clarin.eu/pipermail/ig-fedora/attachments/20201106/3b13db85/attachment-0001.htm>