Hi Pierre,

The "input-forms.xml" was migrated into "submission-forms.xml" in 7.x.  
However, it is *specific* to Item creation, and it will NOT work for 
Collection/Community creation/edit pages.

There is not a single area of code to point you to where the 
"submission-forms.xml" becomes HTML.   Instead, the configuration in 
"sumission-forms.xml" is transformed into JSON responses in the 
/submissionforms REST API 
endpoint: https://github.com/DSpace/RestContract/blob/main/submissionforms.md  
 

Those JSON responses are then read by the UI and translated into the HTML 
forms you see in the Item Submission form -- this is done through a variety 
of *.ts files all under "src/app/submission" 
:  https://github.com/DSpace/dspace-angular/tree/main/src/app/submission

However, all of this is again *specific* to the Item submission process.  
None of this code is used for Collection/Community editing & it'd likely be 
highly complex to adapt it to work for the Collection/Community forms 
(that's not something I can walk you through).

Overall, your conclusion is correct that editing the Collection/Community 
forms currently requires directly modifying the *.ts files which build 
those pages.  Those forms are not dynamically built.

Not sure if that helps any, but that gives an overview of how this all 
works.  (If you need more specific help in this area, you may need to dig 
much deeper into the code or ask more specific questions... I didn't write 
any of this code, so I'm not the foremost expert on the full Item 
Submission UI, but those are the basics)

Tim

On Thursday, September 15, 2022 at 6:34:09 PM UTC-5 [email protected] 
wrote:

> Hi Tim,
>
> I'm trying to programmatically add new fields for the create Community and 
> create Collection pages in DSpace v7.x. I've determined how to use various 
> dynamic controls (e.g. DynamicSelect, DynamicTextArea, etc) to create 
> different types of input fields.
>
> Meanwhile, I can use the xml files to modify and add fields in the create 
> Item page (i.e Edit Submission). This is well-documented, though I've had 
> difficulty with some style issues. For excmpale, I could move the Upload 
> step to the top of the page, but I couldn't make it sticky. 
>
> The Confluence DSpace documentation suggests that "input-forms.xml" was 
> integrated into "submision-forms.xml" in v7.x, but this doesn't seem to be 
> the case. This led to the conclusion that we need to make changes to create 
> Community and create Collection programmatically.
>
> Hence I'm trying to determine how the xml files "item-submission.xml" and 
> "submission-forms.xml" are parsed by the code and converted into HTML. I 
> believe that this will explain how the submission fields are defined for 
> Items via xml and thus how they can be modified programmatically for 
> Collections and Communities,
>
> Can you please point me to where this parsing occurs? It seems to me that 
> this would provide the key to understanding how all of these fields are 
> converted into HTML, either dynamically via .ts files or statically via xml 
> files.
>
> Thanks for your attention,
> -Pierre-
>

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/88c44c10-121d-4e5d-a785-e9b1697086adn%40googlegroups.com.

Reply via email to