# Co-Access Submission: Title and Subtitle issues **URL:** \ **Category:** Content Registration\ **Tags:** content-registration, deposit\_support, title\_update, co-access\ **Created:** [15 June 2023 21:33 UTC](https://community.crossref.org/t/co-access-submission-title-and-subtitle-issues/3690 "2023-06-15T21:33:41Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![ajt\_muse](https://avatars.discourse-cdn.com/v4/letter/a/c67d28/32.png) [@ajt\_muse](https://community.crossref.org/u/ajt_muse)\ **Post date:** [15 June 2023 21:33 UTC](https://community.crossref.org/t/co-access-submission-title-and-subtitle-issues/3690/1 "2023-06-15T21:33:41Z")
Hi All - This has been a long time issue we have dealt with, and I thought I would ask if there is a better/more efficient solution than what we currently do (and keep in mind, our submission process is entirely automated) We frequently have cases where we are not able to submit a DOI for a Co-access book because of an exclusion/inclusion of a book subtitle. For example, we have a book (e-isbn = 9781610758062): title = _Fishing Arkansas_, subtitle = _A Year-Round Guide to Angling Adventures in the Natural State_ On our site we display book titles as “title: subtitle” - in this case: _Fishing Arkansas: A Year-Round Guide to Angling Adventures in the Natural State_ And this is how we submit our DOIs In this particular case, the DOI was already submitted, but with the title of just “Fishing Arkansas” so the result is: _ISBN “9781610758062” has already been assigned, ISBN assigned to other title: Fishing Arkansas/9781610758062Relations processed: 1_ It is almost a flip of the coin if subtitle is or is not included in our Co-Access partnership. The way we handle it, is that we start by including Title: subtitle, but then if that fails we try with just title. This is done programmatically so it is a bit convoluted and not ideal from a maintenance standpoint. Is there any better way to do this? I suppose I could look up the title before I attempt to submit it, but I was hoping to avoid this type of step. Any suggestions would be appreciated. Thanks, Abba ---
**Author:** ![ifarley](https://sea2.discourse-cdn.com/flex020/user_avatar/community.crossref.org/ifarley/32/44_2.png) [@ifarley](https://community.crossref.org/u/ifarley)\ **Post date:** [19 June 2023 17:03 UTC](https://community.crossref.org/t/co-access-submission-title-and-subtitle-issues/3690/2 "2023-06-19T17:03:47Z")
Hi @ajt_muse , Thanks for your message. Best practice is to include the title and subtitle in their own elements, so, in your example, this would be best practice for the title- and subtitle-level XML submitted to us: ```auto Fishing Arkansas A Year-Round Guide to Angling Adventures in the Natural State ``` We only store the `` element in our admin tool title records, and we only use the element for matching in establishing that co-access relationship. So, if one of the members in the co-access partnership/relationship submits the above title using best practice (`<title>` and `<subtitle>`) and then another member attempts to register the title and subtitle all in the `<title>` element (or, vice versa), that subsequent submission will fail. So, you’re right. Our title check process is very rigid. And, not everyone follows best practice, so this is a fairly common issue with members using co-access. You can confirm the title in our system using the Title List here: [crossref.org : : Title List](https://www.crossref.org/titleList/) ![Screenshot 2023-06-19 at 12.00.38 PM](https://us1.discourse-cdn.com/flex020/uploads/crossref/original/2X/d/df344ad4590bdfbd2c60fbba871f52a240a4ad11.png) I wish there were a more efficient way of dealing with this. Unfortunately, I don’t foresee us making changes to our title check process to improve this, since a loosening for co-access would impact title checks for other content types (and, thus, other downstream metadata impacts). Warm regards, Isaac