I want to export the uploaded data (parallel translations) to another project to use as model training, but is unable to find how
-Tried searching on stack overflow and FAQs
All projects within the same workspace share the same data store. You can reuse the data in another project, as long as the language pairs of the original project and the new project are the same.
To move data to another workspace, you will need to download first, then upload to the new workspace.
Related
I am working on a windows store app, one of the workflows within the app would allow the user to export a report in html format. The html report relies on a css file so I would like to ensure that the install process could deploy the file in a local folder. If not I would need to read out the file from the assets folder (within the install bundle) and manually write it out but that seems pretty kludgy
https://learn.microsoft.com/en-us/uwp/api/Windows.Storage.KnownFolders?view=winrt-22000
mentions that "The Documents library is not intended for general use." so would require use through file picker but I would prefer to be able to export the document without user intervention without additional store approval headaches (apparently adding Documents library capability to manifest requires additional Microsoft store approval).
Questions
When I create files within the store app it seems the location options are limited and I can only write to Localfolder (which is actually hidden and users cannot easily get to it) - There must be a way to create a file within the MyDocuments directory that is easily accessible by users but looks like that is off limits to a windows store app? So what is the best approach to write reports to storage that can be easily accessed by users
How can one deploy files to a specific directory during install time? Assuming there are some installer commands/manifest directives that would allow this capability?
Or maybe there is a entirely different mechanism to allow for this functionality within the store app and I am just looking in all the wrong places...
is it possible to transfer files/folders "Hub A" to "Hub B"? Let's say we use Hub A (and C4R) for prototyping purposes, and every month we have to download this prototypes, which is problematic because either the download does not have a directory structure or BIM 360 just never finishes "compressing your items". After downloading and matching the folder structure, we upload this files again to Hub B every time there is a major update to the prototypes.
There is a way to copy files using BIM 360 UI, but just within the same hub.
I would appreciate some guidance here. I've just done some step by step tutorials to get the viewer on my website, so I do not have much experience.
Thanks,
Xavier
Since you ask this question with “Forge Data Management API” tag, so I assume you want to implement the way to achieve that by API.
With the current Data Management API, there is not an easy API to do that directly, but if you want to transfer files/folders from "Hub A" to "Hub B", you can always check & download all the files/folder from "Hub A", and then upload them to "Hub B". There are many details you may need to handle, for example, when the file you want to upload is already there, you can either create a new version or just override it.
We have some similar samples may help you to understand or get started with if you are interested. For example, https://github.com/Autodesk-Forge/data.management-nodejs-integration.box , this is used to exchange files between "Autodesk Hub" and "Box", you can download and check. Also, https://github.com/Developer-Autodesk/data.management-csharp-a360sync , this sample is used to sync the files from local to your A360 account, it's a C# desktop application and is still working in progress as mentioned in README, but, you can get the idea from sample/code anyway.
Hope it helps.
I am familiar with the regular properties APIs for storing app-specific metadata to a file, but is there any way I can store App metadata within drive without linking it to a specific file?
I would prefer to store some configuration settings, but the only approach I've seen for this so far has been to create an actual file in GDrive (and hope the user doesn't delete it).
Is there a more stable approach?
You can store a configuration in you Application Data Folder on Google Drive.
More infos in the actual documentations, but a quick explanation is that you can store files in an hidden folder visible only by your application (any application using the same api key share the same AppData folder).
For example I store a text file with the settings of an Android application, when the user installs it on a different device, the settings are downloaded to the new device.
The approach using a file to store settings let you keep track of the changes made on the configuration by using versions, but if you are more keen to use properties, you can still create an empty app.config file and store properties on it.
I have successfully created tasks using the box-api v2 on files. However, I often need to create a task in a folder, e.g. for someone to upload a file to the folder, not simply review a file in that folder.
It doesn't appear to be possible now, is that true? if so, any plans to make that possible?
It's not possible to assign a task to a folder via the API or the Box web application. I don't believe Box has any current plans to add tasks either via the web or programmatically.
Rory
I have a requirement to build an application with the following features:
Statistical and Source data is presented on simple HTML pages
Some missing Source data can be added from that HTML page ( data will be both exact numerical values and discriptive text )
Some new Source data can be added from those pages
Confirmed and verified data will NOT be editable via the HTML interface
Data is stored and made continuously available via the HTML interface
Periodically the data added/changed from the interface needs to be pulled back into the source data - but in a VERY controlled way. All data changes and submissions will need verification and checking - and some will trigger re-runs of models ( some of which take hours to run ).
In terms of overview architecture I have:
Large DB that stores and manages the data - this is designed for import process's and analysis. It is not ideal for web presentation or interface
Code servers that manipulate the data for imports and analysis
Frontend server that works as a proxy to add layer of security to S3
Collection of generated html files on S3 presenting the data required
Before reading about the Google Drive Realtime API my rough plan was to simply serialize data from the HTML interface and post to S3. The import server scripts would then check for new information, grab it, check it, log it and process it into the main data set.
That basic process however would mean that once changes were submitted from the web page - they would be lost from the users view until they had been processed by the backend.
With the Google Drive Realtime API it would appear I could get the best of both worlds.
However for the above to work I would need to be able to access the Collaboration Document in code from the code servers and export the data.
The Realtime API gives javascript access to Export and hand off to a function - however in my use case I want to automate the Export from the Collaboration Document.
The Google Drive SDK does not as far as I can see give any hints on downloading/exporting a file of type "Collaboration File".
What "non-browser-user" triggered methods are there for interfacing with the Collaboration Documents and exporting them?
David
Server-side export is not supported right now. What you could do is save the realtime model to a regular drive file, and read from that using the standard Drive API. See https://developers.google.com/drive/realtime/models-files for some discussion on different ways to setup interactions between realtime models and Drive Files.