Bug #13476

Problem: AtoM API calls don't work with slugs that use valid characters

Added by David Juhasz 9 months ago. Updated 3 months ago.

Status:QA/ReviewStart date:02/24/2021
Priority:MediumDue date:
Assignee:-% Done:

0%

Category:Web service API
Target version:Release 2.7.0
Google Code Legacy ID: Tested version:2.5, 2.6
Sponsored:No Requires documentation:

Description

Feature #11761: Update slug generation rules include a more permissive option added the option to allow an expanded set of characters in AtoM slugs. The AtoM API however still only recognizes the initial set of lower-case letters, numerals 0-9, and the simple dash "-" as valid for slugs.

To Reproduce

  1. Log in to AtoM as an Administrator
  2. Go to "Admin > Settings" and ensure "Use any valid URI path segment and uppercase character in slugs" is set to "yes"
  3. Create an Archival description with a title containing an underscore (_) character (or another special character) and Save it (e.g. "test_01")
  4. Confirm that the Archival description slug includes the special character
  5. Go to "Admin > Plugins" and ensure the "arRestApiPlugin" is enabled
  6. Generate an API key for a user
  7. Attempt to get your newly created archival description using the API, e.g. curl -H "REST-API-Key: 90e458ded261c7a5" "http://www.example.com/index.php/api/informationobjects/test_01

Resulting error

JSON response:

{
    "id": "not-found",
    "message": "Endpoint not found" 
}

Expected result

The archival description metadata is returned as JSON.


Related issues

Related to Access to Memory (AtoM) - Feature #11761: Update slug generation rules include a more permissive op... Verified 12/01/2017

History

#1 Updated by David Juhasz 9 months ago

  • Related to Feature #11761: Update slug generation rules include a more permissive option added

#2 Updated by Melanie Kung 3 months ago

  • Status changed from New to In progress
  • Assignee set to Melanie Kung

#3 Updated by Melanie Kung 3 months ago

  • Status changed from In progress to Code Review

#5 Updated by Dan Gillean 3 months ago

  • Target version set to Release 2.7.0

#6 Updated by Melanie Kung 3 months ago

  • Status changed from Code Review to QA/Review
  • Assignee deleted (Melanie Kung)

Also available in: Atom PDF