Paulo Graça

Sorry for the absence of my feedback on this PR, I would like help to bring this feature into DSpace, but lately I've being swamped with local stuff and internal...

There is an issue https://github.com/DSpace/DSpace/issues/9402 that is addressed with: https://github.com/DSpace/DSpace/pull/9415 . This PR fixes an issue that limit you to a maximum of 10 collections per entity type (default solr...

A better implementation to the one I did with forms loading, with some associated effort, would be to also consider an alternative way how submission forms are made available. Currently,...

I can confirm that this PR is working and exposing properties 

@mwoodiupui I don't oppose to have it more descriptive. The only reason I raised this is because of the need to translate those labels into our native language and if...

Thank you @kshepherd! But as @benbosman wrote in the PR, the model supports specifying same relation label when having different entities involved in the relationship. I have an use case...

Addressing the Resource Type as entities is one approach, a little more complex IMHO. We are addressing it differently. We choose to use Controlled Vocabularies at the submission form with...

Our solution is shown to the user in this way: 

@pilasou our solution (currently implemented) is based on controlled vocabularies and I think with this DS8 PR https://github.com/DSpace/DSpace/pull/9318 you will be able to address translations with a specific translated xml...

@abollini Your suggestion makes totally sense to me and I'm align with it, but considering it now implies to "throw to trash" most of the work done in the PR....