Redirect https://dlme.clir.org/ to https://spotlight.dlmenetwork.org/

[waynegraham]

Quick clarification question on this. I thought the idea here was for https://www.dlmenetwork.org to be the landing page (e.g. what spotlight.dlmenetwork.org is currently). This would be a separate ticket, but right now www.dlmenetwork.org (and dlmenetwork.org) do not resolve to anything.

I can redirect dlme.clir.org to spotlight.dlmenetwork.org, but wanted to clarify if the redirect should be to spotlight.dlmenetwork.org or www.dlmenetwork.org.

[jacobthill]

I'm not sure @waynegraham. I was under the impression that we were dropping all of the content from dlme.clir.org. We hadn't made plans to translate it, at least. If we redirect to dlmenetwork.org we need to put some content there and probably translate it to Arabic. @anarchivist, @ewaraksa do you recall what the decision was?

[ewaraksa]

I looked around in our meeting notes and it seems we landed on dlme.clir.org being CLIR's responsibility to manage, as it was never mentioned in any agreements with Stanford. We definitely decided that the Spotlight site should be the entry point to the DLME. I think we were strongly leaning towards retiring/archiving the dlme.clir.org site; we also floated having the Spotlight site point back to dlme.clir.org I think it's all up to whether CLIR wants to keep it as an initiative page like e.g. the DLF's, and link to it from Spotlight, or just retire it. I'm personally fine with it being retired, as long as it's been archived somewhere like the Wayback Machine. Thanks, Elizabeth

On Tue, Apr 21, 2020 at 10:05 AM jacobthill notifications@github.com wrote:

I'm not sure @waynegraham https://github.com/waynegraham. I was under the impression that we were dropping all of the content from dlme.clir.org. We hadn't made plans to translate it, at least. If we redirect to dlmenetwork.org we need to put some content there and probably translate it to Arabic. @anarchivist https://github.com/anarchivist, @ewaraksa https://github.com/ewaraksa do you recall what the decision was?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/sul-dlss/dlme/issues/951#issuecomment-617200910, or unsubscribe https://github.com/notifications/unsubscribe-auth/AL4R2CQ23TB5RNSLQWUMFJTRNWRU7ANCNFSM4MJ3J2ZQ .

-- Elizabeth A. Waraksa, Ph.D. Associate Dean Libraries and Academic Innovation The George Washington University 2130 H Street NW, Suite 709 Washington, DC 20052 202-994-5081 ewaraksa@gwu.edu

[waynegraham]

@jacobthill & @ewaraksa We're on the same page, dropping re: dropping content. Definately don't want to keep it around or try to translate it in any way. The intention is just to have www.dlmenetwork.org be the canonical URL (which would probably be another ticket and involve a few other team members).

Right now www.dlmenetwork.org doesn't resolve to anywhere on the Internet which is what some people will guess is the URL for the project. I think www.dlmenetwork.org should resolve to the page that is currently the default at spotlight.dlmenetwork.org (like a ServerAlias in the nginx or apache config).

Then, all content from dlme.clir.org is then redirected to www.dlmenetwork.org (or spotlight.dlmenetwork.org depending on how this is implemented).

[anarchivist]

@waynegraham's proposal immediately above sounds correct to me, too.

@jacobthill: can you make sure this work also gets added to the launch punch list?

[kamchan]

Looking at old email/notes from a year ago and things certainly could have changed since then, the dlmenetwork.org was registered under clir.org in AWS.

To setup spotlight.dlmenetwork.org, we provided the NS and CNAME information to clir to add to the dlmenetwork.org hosted zone for prod/stage/dev

spotlight.dlmenetwork.org spotlight.stage.dlmenetwork.org spotlight.dev.dlmenetwork.org

As far as I understand, we've been managing the spotlight* names. If there were changes since those were setup, we'll need updated info.

[waynegraham]

@kamchan I added the NS entries for www.dlmnetwork.org to have the same entries as spotlight.dlmenetwork.org. Are there additional changes that need to be added?

[kamchan]

@waynegraham The NS/CNAME info I posted earlier was for the process of getting the Stanford's spotlight.dlmenetwork.org subdomain configured under the main dlmenetwork.org domain.

I'm trying to understand the issue here, are we trying to redirect dlmenetwork.org to spotlight.dlmenetwork.org? If that is the case I think it needs to go thru a local S3 bucket for the redirect and have the dlmenetwork.org route53 record point to that s3 bucket.

This gives some steps in doing similar.
https://aws.amazon.com/premiumsupport/knowledge-center/redirect-domain-route-53/

[waynegraham]

@kamchan I think this is two tickets which is leading to some confusion.. The part I believe we need you for is to create www.dlmenetwork.org as a server alias for spotlight.dlmentwork.org.

After that is in place, I will be redirecting dlme.clir.org to www.dlmenetwork.org. The end result here is that www.dlmenetwork.org is the canonical URL for this project (not spotlight.dlmenetwork.org).

[kamchan]

@waynegraham The example given in the link above is probably the preferred way of doing the server alias at the dlmenetwork.org root domain level to point to spotlight.dlmenetwork.org.

Stanford Libraries uses s3 bucket website hosting to perform several redirects to external sites so is used often enough.

Please correct me if I'm not up to date, but as far as I know CLIR owns the dlmenetwork.org root domain? I think it makes sense the s3 bucket that does that redirect is configured within the same AWS environment that houses the dlmenetwork.org root since they are manipulating the dlmenetwork.org domain behavior? I can work with someone with access if there are questions with the instructions in that link.

Thoughts or anyone else has ideas on another approach?

[waynegraham]

I think when we originally registered the domain name, there was some thoughts around keeping this in the hopes of transferring this to another organization in the region to maintain in the long run. However, this has changed and it may be better to transfer the domain so it resides with where the systems folks managing this stack are located to ensure there aren't disconnects from the tech stack and DNS settings.

Would it make sense to initiate a transfer of the domain?

[jacobthill]

@waynegraham I think the domain transfer would make sense. I agree that the team responsible for maintenance should own the domain. I'm not sure about that process. @kamchan @anarchivist what do we need to move forward with this.

[kamchan]

judging by aws documentation

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-transfer-between-aws-accounts.html

looks like CLIR will need to work with aws support to initiate the domain transfer (probably easiest option). On the Stanford side, there're facilities for us to transfer in a domain that is "transferable". We need to carefully coordinate this since dlmenetwork.org is root domain serving spotlight(prod/stage/dev) and once dlmenetwork.org is transferred to Stanford, I imagine there will be outages to all 3 environments and will need to figure what breaks and to actually fix any issues.

Will need coordination throughout.

[kamchan]

dlmenetwork.org should now redirect to spotlight.dlmenetwork.org instead of not getting resolved. The same behavior is true for stage and dev as well.

[kamchan]

@jacobthill @waynegraham

It seems a bit more involved to handle an https://dlmenetwork.org redirect. It will require getting new certs (which really doesn't get used) and putting the s3 bucket behind cloudfront and more route53 changes. Is this totally required? It's not a security issue since dlmenetwork.org just does a redirect with the landing spotlight url using ssl.

So far all our other aws redirects within other projects behave similarly.

[anarchivist]

Just an update - the sites are now served from the following hostnames directly

• Prod: dlmenetwork.org (formerly spotlight.dlmenetwork.org)
• Staging: stage.dlmenetwork.org (formerly spotlight.stage.dlmenetwork.org)
• Development: dev.dlmenetwork.org (formerly spotlight.dev.dlmenetwork.org)

We know we need to retain stories.dlme.clir.org for the time being. @waynegraham are there any further considerations there?