Fix camel case issue for field in export feed

[CarolineDenis]

Fixes #4650

Checklist

• Self-review the PR after opening it to make sure the changes look good
  and self-explanatory (or properly documented)
• Add relevant issue to release milestone

Testing instructions

• delete any existing export feed

• save

• create a new export feed using the visual editor

• switch to xml editor

• verify the collectionId and userId are camel case

• verify that you can do an export

@grantfitzsimmons edit, also test:

• Navigate to a database with an existing export feed (one created before this PR)
• Verify that the export works in edge
• Update the RSS feed from the User Tools menu
• Verify that the export is completed successfully in issue-4650

[maxpatiiuk]

See #4650 (comment)
Instead of adding an exeption on the front-end, we should fix this on the back-end because this is the only place across all XML files where we have camelCase XML attributes rather than lowercase or kebab-case

even worse, some of the attributes in the same XML file are lowercase and some camelCase, which is very inconsistent:

specify7/specifyweb/export/feed.py

Line 39 in f216dae

filename = item_node.attrib['filename']

to fix this inconsistency, without breaking existing XML resources, you can simply change this line:

specify7/specifyweb/export/feed.py

Line 45 in f216dae

collection = Collection.objects.get(id=item_node.attrib['collectionId'])

to

collection = Collection.objects.get(id=item_node.get('collectionid', item_node.get('collectionId')))

(the above will try to get collectionid attribute if it exists, and if not, fallback to

and same for the other 2

[emenslin]

Testing instructions

• delete any existing export feed

• save

• create a new export feed using the visual editor

• switch to xml editor

• verify the collectionId and userId are camel case

• verify that you can do an export

collectionId and userId are not camel case however I was able to export anyway. Is this the new expected behavior? And if so then the first check for testing instructions should be removed.

[grantfitzsimmons]

Testers– please make sure to test this on DBs that already have working export feeds configured:

• Navigate to a database with an existing export feed (one created before this PR)
• Verify that the export works in edge
• Update the RSS feed from the User Tools menu
• Verify that the export is completed successfully in issue-4650

[acwhite211]

I tested with and without camelCase for the RSS Export Feed on the KUFish database, and both seem to work fine. Let me know if anyone finds a case or specific database where it is not working.

[emenslin]

Testing instructions

• delete any existing export feed

• save

• create a new export feed using the visual editor

• switch to xml editor

• verify the collectionId and userId are camel case

• verify that you can do an export

also test:

• Navigate to a database with an existing export feed (one created before this PR)
• Verify that the export works in edge
• Update the RSS feed from the User Tools menu
• Verify that the export is completed successfully in issue-4650

works both with and without camel case

[combs-a]

Testing instructions

• delete any existing export feed

• save

• create a new export feed using the visual editor

• switch to xml editor

• verify the collectionId and userId are camel case

• verify that you can do an export

Also worked with or without camel case for me, was all lowercase by default.

• Navigate to a database with an existing export feed (one created before this PR)
• Verify that the export works in edge
• Update the RSS feed from the User Tools menu
• Verify that the export is completed successfully in issue-4650

Worked perfectly, used sross on herb_rbge_2_5_2024. I had some issues with it on edge, where it'd take awhile to load, but it seems to work better on this PR? And same as above--it went to lowercase, but it seemed to work just fine regardless of camel case or not.

Also stumbled into some unrelated issues related to RSS feeds in general but overall it seems like this is working! Good job!