NXDOC-2184: subpages for Aspera Connector #1549

manonlumeau · 2020-09-10T13:24:37Z

No description provided.

nuxeojenkins · 2020-09-10T13:24:41Z

View issue in JIRA: NXDOC-2184: create doc structure for the aspera add-on

lisamcintyre · 2020-10-06T15:04:27Z

From @RSalem07: Since NXP-29548 and the merge that I did the last week, I forgot to tell you that you can:
remove or put in comment the two lines nuxeo.s3storage.useDirectUpload=true and nuxeo.s3storage.transient.roleArn in your nuxeo.conf
you can also remove the
export ASPERA_AWS_TRANSIENT_BUCKET_ROLE=arn:aws:iam::783725821734:role/l2it-test-gl-aspera-role from you bash profile / env variables , this one was needed to be able to run integration test on our local env against AWS.
I think we should update the documentation, to say that the role and useDirectUpload both of them are not needed.

andreacornaglia · 2020-10-08T09:28:42Z

Locally the layout seems to be breaking, not sure if it's because of the images or some markup hiccup or some local configuration on my side.

manonlumeau · 2020-10-08T09:32:33Z

@andreacornaglia I'll take care of it, when doing my final review :)

andreacornaglia · 2020-10-08T09:37:44Z

src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector.md

+Installation is made of two steps:
+
+1.  Install the [Nuxeo Package](https://connect.nuxeo.com/nuxeo/site/marketplace/package/nuxeo-aspera) available from the marketplace.
+2.  Install the [Aspera desktop client].


is the idea to put a link here?

@andreacornaglia yes, on the 2.0.x doc, there is a dead link. I need to locate a link to the connector that works and validate the version works with our connector.

The Aspera desktop client is required but we don't recommend to do it outside our scope, or do we?
If you don't have it, you'll be prompted on the first time you try to use our connector/integration.

Also, the browser extension is also needed and we are not referring that. Guess we should decide what direction we want to take: state those things or document the wizard

we don't NEED it, necessarily. It was part of the previous documentation. @nmpcunha , good point. I think it's actually a good idea to remove the link and just refer to the fact you will be "prompted to download the necessary software, if you haven't already installed it."

andreacornaglia · 2020-10-08T09:42:03Z

src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector.md

+
+#### Transfer steps
+The process of adding content is divided into 2 steps: **Upload** and **Create**. 
+In the first step, the user **uploads** content to the transfer bucket. While in this step, it may be possible, depending on the chosen “transition type”,  for a user to add files to the bucket and add properties that will apply to the content. 


to add files and folders

andreacornaglia · 2020-10-08T11:14:17Z

src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector.md

+
+> The files uploaded by Aspera will be accessible in this folderish document (by default the target location is the user personal workspace)
+
+Once on the Aspera Upload screen (as you begin to add files), you will be able to download the Aspera Desktop client via the following banner at the top (if not already installed or if a new version is needed):


maybe reword like, the first time using Aspera Upload, you will be prompt a dialog to install Aspera Desktop client....

andreacornaglia · 2020-10-08T11:16:04Z

src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector.md

+
+- [Transfers Dashboard](#transfers-dashboard)
+
+- [Transfers](#transfers)


To avoid confusion, should we rename to something like Aspera Dashboard and Transfer View / Details ?

@andreacornaglia good idea. we'll need to do something since, as we saw in the nike meeting, we'll want to really document what actions do and where they take you.

andreacornaglia · 2020-10-08T11:31:02Z

src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector.md

+This screen shows the status of all current transfers in your Nuxeo application.
+
+You can:
+Create new uploads/transfers


obs: this needs markup to show as a list.

andreacornaglia · 2020-10-08T11:38:41Z

src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector/nuxeo-aspera-upgrade-notes.md

+see [NXP-29282](https://jira.nuxeo.com/browse/nxp-29282)
+
+
+### Storing message files


since we're already linking to the ticket, I would remove from the notes "check code", "code link", "check change".

src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector.md

Co-authored-by: Nuno Cunha <ncunha@nuxeo.com>

nmpcunha · 2020-10-13T09:55:09Z

src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector.md

+We need to configure 2 Aspera nodes; one for upload and one for download.
+
+Each node will be attached to one S3 bucket in Nuxeo:
+- The main Nuxeo S3 bucket in Nuxeo for download purpose


@lisamcintyre , since it is related we should make sure about the download flow as discussed on slack. (i.e. Download will work without S3 Direct Upload?)

@nmpcunha tested a download on master where the files were uploaded just using webui. It worked, so yes, we should be ok.

nmpcunha · 2020-10-13T09:57:36Z

src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector.md

+```
+{{#> callout type='note'}}
+
+Since the work in [NXP-29548](https://jira.nuxeo.com/browse/NXP-29548) 'nuxeo.s3storage.useDirectUpload=true' and 'nuxeo.s3storage.transient.roleArn=' (documented as part of the previous version configuration) are no longer necessary **for the Nuxeo Aspera Connector** and can be removed, **if you only use these values for the Nuxeo Aspera Connector, and not for any other reason**.  See upgrade notes.


Maybe it deserves a link also to the upgrade notes. WDYT?
BTW, please be aware that the ticket does not state any upgrade notes (cc @RSalem07)

PS: @lisamcintyre , this ticket is an internal one, so it won't be accessible 🤷🏼‍♂️

@nmpcunha will work through the links (concerning the upgrade page AND the fact this ticket isn't viewable). will see what makes the most sense to point to for information. Thanks for pointing that out 👍

nmpcunha · 2020-10-13T10:00:51Z

src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector.md

+aspera.node.url=https://ats-aws-us-east-1.aspera.io
+aspera.node.port=443
+
+### ACCESS KEY ON UPLOAD NODE LINKED TO TS S3 BUCKET
+aspera.access.key.id=
+### SECRET KEY ON UPLOAD NODE LINKED TO TS S3 BUCKET
+aspera.access.key.secret=
+
+### ACCESS KEY ON DOWNLOAD NODE LINKED TO TMAIN S3 BUCKET
+aspera.download.access.key.id=
+### SECRET KEY ON DOWNLOAD NODE LINKED TO MAIN S3 BUCKET
+aspera.download.access.key.secret=


I would suggest that we could put values everywhere. Fake ones, or course.
Or simply don't put any value and leave everything empty as above for s3 configs.

Mixing both approaches doesn't make sense IMHO

nmpcunha · 2020-10-13T10:01:59Z

src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector.md

+
+#### Transfer steps
+The process of adding content is divided into 2 steps: **Upload** and **Create**. 
+In the first step, the user **uploads** content to the transfer bucket. While in this step, it may be possible, depending on the chosen “transition type”,  for a user to add files to the bucket and add properties that will apply to the content. 


Check, @andreacornaglia!

Suggested change

In the first step, the user **uploads** content to the transfer bucket. While in this step, it may be possible, depending on the chosen “transition type”, for a user to add files to the bucket and add properties that will apply to the content.

In the first step, the user **uploads** content to the transfer bucket. While in this step, it may be possible, depending on the chosen “transition type”, for a user to add files and folders to the bucket and add properties that will apply to the content.

nmpcunha · 2020-10-13T10:18:30Z

src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector.md

+Once content and any metadata have been added, the transfer can be completed and the content is then **created** in the system.
+
+#### Transfer transition types
+Transitioning between the “upload” and “create” steps can be achieved in 2 ways: **automatically (auto-create)** or **manually**. Users can choose which option to use when creating the transfer from the transfer dashboard.   It is possible to change from manual to auto-create after you start adding content to the transfer.  **Once you set the to auto-create, however, the transfer will behave as if you started in that way, and some limitations around modifying the transfer will apply**.


It is the other way around, right? 🤔

Suggested change

Transitioning between the “upload” and “create” steps can be achieved in 2 ways: **automatically (auto-create)** or **manually**. Users can choose which option to use when creating the transfer from the transfer dashboard. It is possible to change from manual to auto-create after you start adding content to the transfer. **Once you set the to auto-create, however, the transfer will behave as if you started in that way, and some limitations around modifying the transfer will apply**.

Transitioning between the “upload” and “create” steps can be achieved in 2 ways: **automatically (auto-create)** or **manually**. Users can choose which option to use when creating the transfer from the transfer dashboard. It is **not** possible to change from manual to auto-create after you start adding content to the transfer. **Once you set the to auto-create, however, the transfer will behave as if you started in that way, and some limitations around modifying the transfer will apply**.

oy, thanks @nmpcunha that's why we have reviews...

@nmpcunha reading through this...it is as I originally wrote it...you can start with the transfer set to manually complete and keep it there after adding content OR, if you choose, once you started adding content, you can switch to autocreate, BUT from that point, any content you add will be your "last"; the transfer will complete upon THAT content being uploaded.

Not sure If I understood your point, TBH 😕
This sentence doesn't seem clear to me: It is possible to change from manual to auto-create after you start adding content to the transfer.

Because we can't, right? Or am I missing something here? 🤔

@nmpcunha I'm almost positive that we could at one time. I just tested though, and you're correct 😄 . at one time, I thought we had that so that if you had folders at different "root" locations in your finder/explorer, you could do part (grab one root), then change to auto and then get the other root location. I will modify the documentation 👍

nmpcunha · 2020-10-13T10:19:39Z

src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector.md

+#### Transfer transition types
+Transitioning between the “upload” and “create” steps can be achieved in 2 ways: **automatically (auto-create)** or **manually**. Users can choose which option to use when creating the transfer from the transfer dashboard.   It is possible to change from manual to auto-create after you start adding content to the transfer.  **Once you set the to auto-create, however, the transfer will behave as if you started in that way, and some limitations around modifying the transfer will apply**.
+
+When auto-create is toggled/selected to be “on”, the user needs only to start the upload of the folders/files to the transfer.  Once the upload is completed, the system will automatically start the process to create the content in the system; no need to wait around simply to push a button.  **Before adding content** to the transfer, you can edit the **“common metadata”** which would apply to all files in the transfer.  Users can, of course, decide not to include any metadata at all, and simply add files, too.


For consistency purposes should we use content or files and folders?

Suggested change

When auto-create is toggled/selected to be “on”, the user needs only to start the upload of the folders/files to the transfer. Once the upload is completed, the system will automatically start the process to create the content in the system; no need to wait around simply to push a button. **Before adding content** to the transfer, you can edit the **“common metadata”** which would apply to all files in the transfer. Users can, of course, decide not to include any metadata at all, and simply add files, too.

When auto-create is toggled/selected to be “on”, the user needs only to start the upload of the content to the transfer. Once the upload is completed, the system will automatically start the process to create the content in the system; no need to wait around simply to push a button. **Before adding content** to the transfer, you can edit the **“common metadata”** which would apply to all files in the transfer. Users can, of course, decide not to include any metadata at all, and simply add files, too.

I was going to say let's use files and folders, but the more I think about it, "content" might be a better word; it's more inclusive of the various types of "stuff". By that, I mean, that since we should rely on the import/file manager and any business rules that apply for determining the "doc type", stating "files and folders" could be a little "limiting". sure, the content in the transfer is comprised of files and folders, but what they are once they get into the repo might be something that extends those types and not referred to as simply "file" or "folder".

nmpcunha · 2020-10-13T10:22:40Z

src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector.md

+If a user has content that needs to be “tagged” or “catalogued” with metadata before creation in the system, the “manual” transition option might be a better choice. To use the **manual option**, choose “no” for auto-create or toggle the auto-create to “off” when creating a new transfer (you can only turn off auto-create if there is **no content in the transfer)**.  This will require someone **manually start** the creation process by clicking the **“complete transfer”** button once the upload is finished (the button is only visible once there is no longer an upload in progress)
+When using the manual transition, the user uploads content to the transfer bucket. While in this step, a user can add folders and files to the bucket and add properties that apply to the files. Properties can be added that apply to all files using the “common metadata” panel; more file-specific properties can be added either to multiple files at once (bulk edit of metadata) and/or individually,  using a single-file action.
+Once the metadata has been edited to fit the user's needs, the transfer can be **completed** and the content is then created in the system.
+Transfers have 3 states: Draft (no content added yet), In Progress (content added) and Completed (the transfer has been completed and the content has been created in the system).


More or less... 😅
We have more states, even visually. Right?

When we create a transfer it is on "draft".
When we are uploading files it says "Started".
When we press "complete" it would show "Pending".
When everything is done is says "Completed".

@nmpcunha more or less, but I don't believe we show the "draft" state anymore. we only show a status icon for started/pending/completed. showing the draft state was too confusing. this is the draft state (and on the dash, we just have the actions). Remember, this is just the "functional" info at this point. : )

Indeed, there is nothing right now stating "Draft", which may be also tricky from a functional perspective to state that.
Anyway, what does make sense to state as states from a "functional perspective"?

I am wondering if we can summarise those scenarios in a given table,

it's mainly a suggestion / proposal but we can live with the description :)

yes, will remove the reference to the "draft" state (since we don't visualize it) and focus on what we do see (pending/started/completed for now, I believe).. I think once we get our LC states redone for transfers, then a table will be the best way to summarize and can make it similar in "function" to the sheet we have on our wiki page and include manual/auto create info, too.

nmpcunha · 2020-10-14T08:56:29Z

src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector.md

+
+Once in your instance, Nuxeo Aspera Upload can be accessed from two different ways:
+
+- From the **User Settings** menu located on the left side:


This one goes to the dashboard

"it depends". it goes to the last aspera view you were in. if I'm in a trnasfer (not on the dashboard) and then i go to the domain and browse, THEN go to the user settings/aspera dashboard, i land in the transfer I was last in (i just validated on master). not sure i that is was you were addressing here : )

Guess it is a bug then and we should address 😅
If it says "Aspera Dashboard" it should direct the user to the dashboard 🤷🏼‍♂️

nmpcunha · 2020-10-14T08:57:03Z

src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector.md

+--}}
+![aspera-image3](nx_asset://2a6ee847-e886-4047-8e82-f4cafda627eb ?border=true)
+
+- By clicking on the Aspera upload button displayed on every folderish document (workspace, folder, etc.)


But this one will create a new transfer with the folderish as destination!

Do you think it worths to explain that?

(As it was explained on line 296)

yes! as we saw with nike call i did. Thanks for reminding me!

src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector.md

nmpcunha · 2020-10-14T09:04:16Z

src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector.md


 The Nuxeo Aspera Connector uses "Transfers" to add content to the system.

 The process is divided into 2 steps: Upload and Create.

-In the first step, the user **uploads** content to the transfer bucket. While in this step, he can add files to the bucket and add properties that will apply to the content. Properties can be added to all files at once (common metadata), to multiple files at once (bulk edit of metadata) and one at a time.
+In the first step, the user **uploads** content to the transfer bucket. While in this step, a user can add content to the bucket and add properties that will apply to the content. Properties can be added to all files at once (common metadata), to multiple files at once (bulk edit of metadata) and one at a time.


This version only allows files, right? Not sure if using content is clear enough since we use it above with a different meaning 🤔

yes, thanks. I realized i got a little "find" edit happy within my doc pages after I got to a place where I saw a typo and said "I could swear I fixed that" and then i realized i was down in the 2.0.x area. I thought I backed out my changes. wil review. 👍

nmpcunha · 2020-10-14T09:04:30Z

src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector.md

@@ -210,7 +585,7 @@ Once in your instance, Nuxeo Aspera Upload can be accessed from two different wa
 --}}
 ![2-aspera.png](nx_asset://baeef2eb-ddbc-41e1-b036-46ee567027bf ?w=450,border=true)

-> The files uploaded by Aspera will be accessible in this folderish document (by default the target location is the user personal workspace)
+> The content uploaded by Aspera will be accessible in this folderish document (by default the target location is the user personal workspace)


Same question as above

nmpcunha · 2020-10-14T09:04:57Z

src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector.md


 This screen shows the status of all current transfers in your Nuxeo application.</br>

 You can:
- Access the transfer metadata and files properties
+
+- Access the transfer metadata and content's properties


Same files vs content question 😅

src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector/nuxeo-aspera-release-notes.md

nmpcunha · 2020-10-14T09:20:50Z

src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector/nuxeo-aspera-release-notes.md

+
+
+### Folder upload support
+Now, in addition to files, users have the ability to upload content in folders as well as files.  As with files, the upload/creation honors configurations of your file import manager and will apply document types and metadata based on your business rules.


Would this be more clear? WDYT?

Suggested change

Now, in addition to files, users have the ability to upload content in folders as well as files. As with files, the upload/creation honors configurations of your file import manager and will apply document types and metadata based on your business rules.

Now, in addition to files, users have the ability to upload folders and their content as well as files. As with files, the upload/creation honors configurations of your file import manager and will apply document types and metadata based on your business rules.

nmpcunha · 2020-10-14T09:27:36Z

src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector/nuxeo-aspera-upgrade-notes.md

+For a listing of improvements and functional enhancements in version 3.0.x, please see the [release notes]() {{! /excerpt}}
+
+{{#> callout type='warning'}}
+Because of the changes to parameters in the nuxeo.conf file, this release is labeled as a major release.  Transfers that exist in your system **that were started/created with a previous version will not work with this release and attempts to complete them will fail with this realse**.


It was not only due to the parameters change, but also to code/APIs changes.
Maybe it worths to refer that since then, below, we talk about them.

...with this realse-> with this release

nmpcunha · 2020-10-14T09:30:27Z

src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector/nuxeo-aspera-upgrade-notes.md

+For a listing of improvements and functional enhancements in version 3.0.x, please see the [release notes]() {{! /excerpt}}
+
+{{#> callout type='warning'}}
+Because of the changes to parameters in the nuxeo.conf file, this release is labeled as a major release.  Transfers that exist in your system **that were started/created with a previous version will not work with this release and attempts to complete them will fail with this realse**.


Suggested change

Because of the changes to parameters in the nuxeo.conf file, this release is labeled as a major release. Transfers that exist in your system **that were started/created with a previous version will not work with this release and attempts to complete them will fail with this realse**.

Because of the changes to parameters in the **nuxeo.conf** file and also to some API's deprecation and major changes, this release is labeled as a major release. Transfers that exist in your system **that were started/created with a previous version will not work with this release and attempts to complete them will fail with this release**. It is recommended to don't update the Connector version with _ongoing_ transfers.

I like your suggestion, but need to change the wording just a bit so can't commit suggestion directly 👍

nmpcunha · 2020-10-14T09:32:07Z

src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector/nuxeo-aspera-upgrade-notes.md

+
+### Requirements
+- Aspera Desktop Client - [latest version]
+- Nuxeo Server LTS 2019 (10.10, HF 31, at least) with access to AWS S3 Storage along with the [Amazon S3 Online Storage plugin](https://connect.nuxeo.com/nuxeo/site/marketplace/package/amazon-s3-online-storage?version=11.2.13)


Guess the amazon-s3-online-storage version is not the correct one. That's for 11.x or am I missing something?

Guess the most up to date version for 10.10 would be 1.9.12

i just did the link for the connector, I think it must grab the latest by default. will be sure to grab the specific one for 10. 👍

nmpcunha · 2020-10-14T09:33:53Z

src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector/nuxeo-aspera-upgrade-notes.md

+### Transfer edit
+Removed `nuxeo-aspera-upload-edit-dialog` element
+
+see [NXP-28207](https://jira.nuxeo.com/browse/nxp-28207


Broken link!

Suggested change

see [NXP-28207](https://jira.nuxeo.com/browse/nxp-28207

see [NXP-28207](https://jira.nuxeo.com/browse/nxp-28207)

Co-authored-by: Nuno Cunha <ncunha@nuxeo.com>

RSalem07 · 2020-10-15T12:08:04Z

src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector.md

@@ -14,24 +14,399 @@ tree_item_index: 1100

 {{! excerpt}}
 The [Nuxeo Aspera](https://connect.nuxeo.com/nuxeo/site/marketplace/package/nuxeo-aspera) connector
-enables users to download/upload binaries with Aspera.
+enables users to download/upload binaries with Aspera.  It is designed to be used with **Aspera On Cloud** instances, however, if you use a **self-hosted Aspera** instance, it is still possible you will be able to use the Nuxeo Aspera Connector.  Contact your Aspera team for more information and assistance.


I am wondering if we should or not :) add the Aspera link documentation to Aspera On Cloud

@RSalem07 good idea. would help us really "hit home" about the fact this is geared to AOC.

RSalem07 · 2020-10-15T12:10:11Z

src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector.md

+
+- Aspera Desktop Client - you will be prompted to install necessary versions when using the Connector.
+- Nuxeo Server LTS 2019 (**10.10, HF 31, at least**) with access to AWS S3 Storage along with the [Amazon S3 Online Storage plugin](https://connect.nuxeo.com/nuxeo/site/marketplace/package/amazon-s3-online-storage?version=11.2.13)
+- IBM Aspera on Cloud Subscription (see note above about Aspera self-hosted)


About Amazone S3 Online Storage I think we should give the link for the expected version for LTS 2019
https://connect.nuxeo.com/nuxeo/site/marketplace/package/amazon-s3-online-storage?version=1.9.12 instead of 11.2.13

RSalem07 · 2020-10-15T12:11:23Z

src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector.md

+
+{{#> callout type='warning'}}
+If you are **upgrading from a previous version** of the Nuxeo Aspera connector, please see the [upgrade notes](https://doc.nuxeo.com/nxdoc/nuxeo-aspera-connector/nuxeo-aspera-upgrade-notes/) for critical information related to potential breaking code.
+{{/callout}}


The release not is not yet available, isn't it ?

not 3.0 but previous ones, yes.

src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector.md

RSalem07

Thanks Lisa for the work, Left some comments / suggestions

…lease-notes.md Co-authored-by: Nuno Cunha <ncunha@nuxeo.com>

Co-authored-by: Salem Aouana <46494950+RSalem07@users.noreply.github.com>

Fix NXDOC-2184: subpages for Aspera Connector

88e326d

added v 3.0.0 info and screenshots

ffcd5ca

lisamcintyre marked this pull request as ready for review October 2, 2020 19:55

manonlumeau requested review from nmpcunha and andreacornaglia October 5, 2020 15:29

manonlumeau added the Ready for Review label Oct 5, 2020

added release and upgrade pages

8eaf6e0

andreacornaglia reviewed Oct 8, 2020

View reviewed changes

NXDOC-2184: aspera upgrade notes update

9e016bd

nmpcunha reviewed Oct 12, 2020

View reviewed changes

src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector.md Outdated Show resolved Hide resolved

nmpcunha reviewed Oct 12, 2020

View reviewed changes

src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector.md Outdated Show resolved Hide resolved

lisamcintyre and others added 3 commits October 12, 2020 13:31

Update src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector.md

74a8397

Co-authored-by: Nuno Cunha <ncunha@nuxeo.com>

Update src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector.md

a256639

Co-authored-by: Nuno Cunha <ncunha@nuxeo.com>

edits based on feedback

7469b04

nmpcunha reviewed Oct 13, 2020

View reviewed changes

edits based on initial feedback from Andrea and Nuno

92be4b7

nmpcunha reviewed Oct 14, 2020

View reviewed changes

src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector.md Outdated Show resolved Hide resolved

nmpcunha reviewed Oct 14, 2020

View reviewed changes

src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector/nuxeo-aspera-release-notes.md Outdated Show resolved Hide resolved

nmpcunha reviewed Oct 14, 2020

View reviewed changes

Update src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector.md

5de4f3f

Co-authored-by: Nuno Cunha <ncunha@nuxeo.com>

nmpcunha requested a review from RSalem07 October 15, 2020 10:40

RSalem07 reviewed Oct 15, 2020

View reviewed changes

src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector.md Outdated Show resolved Hide resolved

RSalem07 reviewed Oct 15, 2020

View reviewed changes

lisamcintyre and others added 4 commits October 16, 2020 12:44

Update src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector/nuxeo-aspera-re…

64bf392

…lease-notes.md Co-authored-by: Nuno Cunha <ncunha@nuxeo.com>

Update src/nxdoc/nuxeo-add-ons/nuxeo-aspera-connector.md

c5b3783

Co-authored-by: Salem Aouana <46494950+RSalem07@users.noreply.github.com>

final edits based on reviews

5e43d71

Final review Aspera doc

155b694

manonlumeau merged commit fd5d870 into 1010 Nov 16, 2020

manonlumeau deleted the NXDOC-2184-aspera-doc branch November 16, 2020 21:24


		> The files uploaded by Aspera will be accessible in this folderish document (by default the target location is the user personal workspace)

		Once on the Aspera Upload screen (as you begin to add files), you will be able to download the Aspera Desktop client via the following banner at the top (if not already installed or if a new version is needed):


		- [Transfers Dashboard](#transfers-dashboard)

		- [Transfers](#transfers)

		see [NXP-29282](https://jira.nuxeo.com/browse/nxp-29282)


		### Storing message files

	In the first step, the user uploads content to the transfer bucket. While in this step, it may be possible, depending on the chosen “transition type”, for a user to add files to the bucket and add properties that will apply to the content.
	In the first step, the user uploads content to the transfer bucket. While in this step, it may be possible, depending on the chosen “transition type”, for a user to add files and folders to the bucket and add properties that will apply to the content.


		Once in your instance, Nuxeo Aspera Upload can be accessed from two different ways:

		- From the User Settings menu located on the left side:



		### Folder upload support
		Now, in addition to files, users have the ability to upload content in folders as well as files. As with files, the upload/creation honors configurations of your file import manager and will apply document types and metadata based on your business rules.

	see [NXP-28207](https://jira.nuxeo.com/browse/nxp-28207
	see [NXP-28207](https://jira.nuxeo.com/browse/nxp-28207)

NXDOC-2184: subpages for Aspera Connector #1549

NXDOC-2184: subpages for Aspera Connector #1549

Conversation

manonlumeau commented Sep 10, 2020

nuxeojenkins commented Sep 10, 2020

lisamcintyre commented Oct 6, 2020 • edited by manonlumeau

andreacornaglia commented Oct 8, 2020 • edited

manonlumeau commented Oct 8, 2020

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

nmpcunha Oct 15, 2020 • edited

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

lisamcintyre Oct 13, 2020 • edited

Choose a reason for hiding this comment

nmpcunha Oct 13, 2020 • edited

Choose a reason for hiding this comment

lisamcintyre Oct 13, 2020 • edited

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

nmpcunha Oct 14, 2020 • edited

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

nmpcunha Oct 14, 2020 • edited

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

RSalem07 left a comment

Choose a reason for hiding this comment

lisamcintyre commented Oct 6, 2020 •

edited by manonlumeau

andreacornaglia commented Oct 8, 2020 •

edited

nmpcunha Oct 15, 2020 •

edited

lisamcintyre Oct 13, 2020 •

edited

nmpcunha Oct 13, 2020 •

edited

lisamcintyre Oct 13, 2020 •

edited

nmpcunha Oct 14, 2020 •

edited

nmpcunha Oct 14, 2020 •

edited