@Julian Ladisch, that seems like a fine workaround. I do not agree with with a better solution suggestion. I do not think a hot-key should be created to jump to a field.

This issue does not need to be reopened.
There is a workaround: Closing the administrative data section accordion allows to quickly skip the contained fields.
A better solution than altering the inital focus position is to have a hot-key so that the user can directly jump to the title field.

@Julian Ladisch, I cannot find an UX pattern whereby initial focus on a form bypasses 9 fields. Also this change may result in the tab order not being logical AND from a screenreader perspective it may read Save/Close button before it reads the Administrative data section. Also I defer to @Charlotte Whitt, on the frequent use of those 9 fields bypassed. As I stated before, if resource title is the most important field, then it should be the first field on the form.

@Khalilah Gambrell Can you please elaborate why WCAG 2.4.3 disallows setting the inital focus/cursor into the title field? The tab order is still the same.
WCAG 2.4.3 Focus Order says:

If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.

WAI-ARIA Authoring Practices says:

When a dialog opens, focus placement depends on the nature and size of the content.

it may be advisable to set focus to the element that is likely to be most frequently used

Agree. I'll close the ticket as Won't do, then.