Assigned
Status Update
Comments
bl...@google.com <bl...@google.com> #2
Metadata
- Summary: The Directory API's users.list method is inconsistently returning a nextPageToken when using the query parameter, and the starts with operator is not working for the orgDepartment field.
- Tags:
,directory-api ,users-list ,next-page-token ,query-parameter ,org-department starts-with-operator
Additional resources:
https://issuetracker.google.com/savedsearches/566232?hl=it https://developers.google.com/drive/api/reference/rest/v3/files/list https://developers.google.com/admin-sdk/directory/v1/.../manage-users https://developers.google.com/admin-sdk/directory/reference/rest/v1/.../list https://stackoverflow.com/.../want-admindirectory-users-list-more-then-500... https://stackoverflow.com/.../drive-list-files-doesnt-have-nextpagetoken-wh... https://stackoverflow.com/.../how-to-resolve-the-missing-information-probl...
Description
Before opening a new issue, please search for other related issues , click the ★ to subscribe to updates, and click
+1
to vote.Description
Problem Statement: Previously, in Classic Google Sites, users could set custom URLs (e.g.,https://sites.google.edu/a/my-domain ) to present their organization's URL, allowing for various developments to propagate under the organization's domain (e.g., sites.my-domain.edu). While this option remains in the Admin settings of Google Workspace, it targets Classic Sites, which are now out of service.
Desired Behavior: Within our organization, we seek a similar function for the NEW GOOGLE SITES. Faculties are encouraged to develop their Academic Digital Portfolios within the organization's framework, while maintaining personal ownership. Simplifying this process would enhance digital literacy and data ownership quality.
Possible Solution: Implementing such a function would provide a valuable service, allowing for URLs like portfolios.my-domain.com/a-faculty-member. This feature, inherited from Classic Sites, would support both secure service protocols (HTTPS) and normal HTTP.
Possible Alternative: A few years ago, I submitted feedback to the Feature Request suggesting the addition of a new type of FOLDER to Google Workspace for new SITES. When created, this folder's name could default to a subdomain of my-domain.edu. Any SITES created within this folder would appear as children under the subdomain. For instance, creating a folder named PORTFOLIOS would result in faculty portfolios being placed within it, with distribution URLs likehttps://portfolios.my-domain.edu/a-faculty-portfolio .
Or, a FOLDER for CONFERENCES would contain all conference SITES to be presented as
https://conferences.my-domain.edu/conference-1
https://conferences.my-domain.edu/conference-2
Impact
This enhancement would add significant value to Google Workspace, offering flexibility in either mapping a created site or presenting it as a child of a subdomain within the organization. It would facilitate professional use of Google Sites for presenting research, portfolios, events, seminars, and panels while maintaining the organization's framework.